From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Chris Li <sparse@chrisli.org>
Cc: Daniel Gomez <da.gomez@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Sami Tolvanen <samitolvanen@google.com>,
linux-sparse@vger.kernel.org, Aaron Tomlin <atomlin@atomlin.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Eric Biggers <ebiggers@kernel.org>,
linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
"Luck, Tony" <tony.luck@intel.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>
Subject: Re: [PATCH] builtin: mark __builtin_strlen() as integer constant expression
Date: Tue, 24 Feb 2026 12:26:07 +0200 [thread overview]
Message-ID: <aZ18v6V97ROtJPkq@smile.fi.intel.com> (raw)
In-Reply-To: <CACePvbU5ByoP2jZZSHYWCncNNXOQXArvyWpVcinTRag8k3-GiA@mail.gmail.com>
On Fri, Feb 20, 2026 at 11:34:29AM -0800, Chris Li wrote:
> On Fri, Feb 20, 2026 at 12:31 AM Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> > On Fri, Feb 20, 2026 at 12:06:15AM -0800, Chris Li wrote:
> > > On Thu, Feb 19, 2026 at 11:20 AM Andy Shevchenko
> > > <andriy.shevchenko@intel.com> wrote:
> > > > On Thu, Feb 19, 2026 at 09:06:23AM -0800, Chris Li wrote:
> > > > > On Thu, Feb 19, 2026 at 9:00 AM Daniel Gomez <da.gomez@kernel.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 pushed 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.
It seems that your tip is the same as Al's, and if it's the case
we are testing (actually using) this for a few weeks without problems.
Thanks!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-24 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 16:10 [PATCH] builtin: mark __builtin_strlen() as integer constant expression Daniel Gomez
2026-02-19 16:41 ` Sami Tolvanen
2026-02-19 17:00 ` Daniel Gomez
2026-02-19 17:06 ` Chris Li
2026-02-19 19:20 ` Andy Shevchenko
2026-02-20 8:06 ` Chris Li
2026-02-20 8:30 ` Andy Shevchenko
2026-02-20 19:34 ` Chris Li
2026-02-24 10:26 ` Andy Shevchenko [this message]
2026-02-19 16:53 ` Daniel Gomez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aZ18v6V97ROtJPkq@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=atomlin@atomlin.com \
--cc=da.gomez@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=sparse@chrisli.org \
--cc=tony.luck@intel.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox