[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wg9pxiKm3kcZ0XQrFvz6fFek_A1WGqRh9yeghx3pE2d3w@mail.gmail.com>
Date: Thu, 15 Jan 2026 13:19:14 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Thomas Gleixner <tglx@...nel.org>, kernel test robot <lkp@...el.com>, Ian Rogers <irogers@...gle.com>,
oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org, x86@...nel.org,
sparse@...isli.org, linux-sparse@...r.kernel.org,
Marco Elver <elver@...gle.com>
Subject: Re: [tip:timers/vdso 12/14] net/rds/ib_cm.c:96:35: sparse: sparse:
incorrect type in argument 1 (different modifiers)
On Thu, 15 Jan 2026 at 13:13, Peter Zijlstra <peterz@...radead.org> wrote:
>
> Something like so perhaps, which then mandates the very latest Sparse.
Ack. We want that compiler_tpes.h change for the real compilers that
support __typeof_unqual__ anyway.
Eventually we can just force that everywhere, but as Al pointed out in
another thread, we're not quite there yet (ie we'd need clang-19.0.1
and gcc-8.4 to be able to just switch entirely over to
__typeof_unqual__).
For sparse users, I think we should have the policy that we just don't
support older versions at all, since it just gets too painful.
Linus
Powered by blists - more mailing lists