From: Vincent Mailhol <mailhol@kernel.org>
To: Philip Li <philip.li@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Chris Li <sparse@chrisli.org>, Al Viro <viro@zeniv.linux.org.uk>
Cc: David Laight <david.laight.linux@gmail.com>,
kernel test robot <lkp@intel.com>,
Nathan Chancellor <nathan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
Yury Norov <yury.norov@gmail.com>,
Jani Nikula <jani.nikula@intel.com>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH next 11/14] bit: Strengthen compile-time tests in GENMASK() and BIT()
Date: Fri, 23 Jan 2026 09:01:04 +0100 [thread overview]
Message-ID: <b49c9993-7676-4d33-a2d6-9f6b77b0fd34@kernel.org> (raw)
In-Reply-To: <aXLOELiIG8MHKcIO@rli9-mobl>
Adding the relevant parties to the discussion:
+To: Al Viro
+To: Chris Li
On 23/01/2026 at 02:25, Philip Li wrote:
> On Thu, Jan 22, 2026 at 04:26:44PM +0200, Andy Shevchenko wrote:
>> On Thu, Jan 22, 2026 at 10:33:37AM +0000, David Laight wrote:
>>> On Thu, 22 Jan 2026 12:41:22 +0800
>>> kernel test robot <lkp@intel.com> wrote:
>>
>>>> sparse warnings: (new ones prefixed by >>)
>>>> kernel/kthread.c: note: in included file (through include/linux/bitmap.h, include/linux/cpumask.h, arch/mips/include/asm/processor.h, ...):
>>>>>> include/linux/find.h:209:45: sparse: sparse: Variable length array is used.
>>>
>>> Can we stop sparse complaining about sizeof(VLA) ?
>>
>> First of all, the LKP should install the fork of sparse by Al Viro. That will
>> fix tons of warnings that are related to modules and speed up the process
>> itself.
>
> Thanks Andy, i will switch to the repo from Al Viro for sparse.
Al Viro's fork just adds 8 commit on top of the upstream sparse repo.
Wouldn't it be possible to just merge those?
That would be much less confusing.
Yours sincerely,
Vincent Mailhol
next prev parent reply other threads:[~2026-01-23 8:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260121145731.3623-12-david.laight.linux@gmail.com>
2026-01-22 1:11 ` kernel test robot
2026-01-22 10:25 ` David Laight
2026-01-22 20:10 ` David Laight
2026-01-22 4:41 ` kernel test robot
2026-01-22 10:33 ` David Laight
2026-01-22 14:26 ` Andy Shevchenko
2026-01-22 14:55 ` David Laight
2026-01-23 1:25 ` Philip Li
2026-01-23 8:01 ` Vincent Mailhol [this message]
2026-01-23 8:11 ` Andy Shevchenko
2026-01-23 8:20 ` Al Viro
2026-01-23 8:24 ` Andy Shevchenko
2026-01-23 8:32 ` Vincent Mailhol
2026-01-23 8:46 ` Andy Shevchenko
2026-01-23 1:24 ` Philip Li
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=b49c9993-7676-4d33-a2d6-9f6b77b0fd34@kernel.org \
--to=mailhol@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=david.laight.linux@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@intel.com \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=nathan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=philip.li@intel.com \
--cc=sparse@chrisli.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=yury.norov@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