From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>,
Dan Carpenter <dan.carpenter@linaro.org>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-sparse@vger.kernel.org
Subject: Re: issue with _Static_assert and __builtin()s
Date: Tue, 10 Feb 2026 06:40:47 -0800 [thread overview]
Message-ID: <4121dfdc-a1b4-49da-83e5-1042950dea6d@oss.qualcomm.com> (raw)
In-Reply-To: <1b4aab7e-28ad-4b8f-a2f4-fac639e923bb@codethink.co.uk>
On 2/10/2026 6:25 AM, Ben Dooks wrote:
> On 09/02/2026 16:25, Jeff Johnson wrote:
>> Al: Will you be contributing this fix (and perhaps the rest of your
>> accumulated changes) to linux-sparse?
> And are there any other goodies in that tree?
There are...
https://git.kernel.org/pub/scm/linux/kernel/git/viro/sparse.git/log/
prev parent reply other threads:[~2026-02-10 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 19:41 issue with _Static_assert and __builtin()s Ben Dooks
2026-01-08 5:41 ` Dan Carpenter
2026-01-08 9:38 ` Ben Dooks
2026-02-09 16:25 ` Jeff Johnson
2026-02-10 14:25 ` Ben Dooks
2026-02-10 14:40 ` Jeff Johnson [this message]
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=4121dfdc-a1b4-49da-83e5-1042950dea6d@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ben.dooks@codethink.co.uk \
--cc=dan.carpenter@linaro.org \
--cc=linux-sparse@vger.kernel.org \
--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