From: Al Viro <viro@zeniv.linux.org.uk>
To: Steve French <smfrench@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: new noisy sparse warnings building 7.0-rc1
Date: Thu, 26 Feb 2026 19:14:53 +0000 [thread overview]
Message-ID: <20260226191453.GA3836593@ZenIV> (raw)
In-Reply-To: <CAH2r5mub=QA=7fXxHuvZpbzX+gvyf3zEJpDcaHAxwCwrir9d7A@mail.gmail.com>
On Thu, Feb 26, 2026 at 10:47:49AM -0600, Steve French wrote:
> I see some very noisy sparse warnings building 7.0-rc1
>
> Any ideas how to avoid them?
Sigh... __VA_OPT__ is currently unsupported in sparse; I have a stalled
branch adding that (from back in December), hopefully will have something
usable posted in a few days.
prev parent reply other threads:[~2026-02-26 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 16:47 new noisy sparse warnings building 7.0-rc1 Steve French
2026-02-26 19:14 ` Al Viro [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=20260226191453.GA3836593@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@gmail.com \
/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