Re: [PATCH] builtin: mark __builtin_strlen() as integer constant expression
Chris Li <[email protected]> Fri, 20 Feb 2026 11:34:29 -0800
| Newsgroups | org.kernel.vger.linux-sparse,org.kernel.vger.linux-kernel,org.kernel.vger.linux-modules |
|---|---|
| Message-ID | <CACePvbU5ByoP2jZZSHYWCncNNXOQXArvyWpVcinTRag8k3-GiA@mail.gmail.com> |
On Fri, Feb 20, 2026 at 12:31=E2=80=AFAM Andy Shevchenko <[email protected]> wrote: > > On Fri, Feb 20, 2026 at 12:06:15AM -0800, Chris Li wrote: > > On Thu, Feb 19, 2026 at 11:20=E2=80=AFAM Andy Shevchenko > > <[email protected]> wrote: > > > > > > On Thu, Feb 19, 2026 at 09:06:23AM -0800, Chris Li wrote: > > > > On Thu, Feb 19, 2026 at 9:00=E2=80=AFAM Daniel Gomez <da.gomez@kern= el.org> wrote: > > > > > > > > > > Can you please take a look? If Al patch is the correct approach, = any > > > > > chance you can send it and fix this? > > > > > > > > I am asking in another thread should I pull Al's git repo instead. > > > > There are a few good commits there. > > > > > > Please, pull Al's work, My colleagues and I use his version of sparse= for a few > > > weeks without noticing any downsides. > > > > Thanks for the heads up. I just pulled Al's sparse repo. > > Can you also issue a new tag (say 0.6.5) so the distros can really be pus= hed to > update the quite outdated sparse in their repos? Sure. I can give it a spin this weekend and keep you posted. There is one risk on my signing key, it might be expired and I need to sort that out. Meanwhile, please give the current sparse repo some good tests. Chris