From: Nathan Chancellor <nathan@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Marco Elver <elver@google.com>,
Bart Van Assche <bvanassche@acm.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
pkg-llvm-team@lists.alioth.debian.org
Subject: Re: [PATCH] lib/Kconfig.debug: Require a release version of LLVM 22 for context analysis
Date: Wed, 25 Feb 2026 11:53:57 -0700 [thread overview]
Message-ID: <20260225185357.GA2755225@ax162> (raw)
In-Reply-To: <20260225145228.GB1282955@noisy.programming.kicks-ass.net>
On Wed, Feb 25, 2026 at 03:52:28PM +0100, Peter Zijlstra wrote:
> On Tue, Feb 24, 2026 at 04:16:30PM -0700, Nathan Chancellor wrote:
> > Using a prerelease version as a minimum supported version for
> > Peter, could you take this for a 7.0-rc?
>
> Yes, I can.
Thanks a lot!
> I would however appreciate the Debian folks to quickly push an update
> to the clang-22/experimental package. Otherwise I can't run this fancy
> stuff myself no moar.
https://packages.debian.org/experimental/clang-22
claims that the experimental clang-22 package is at 22.1.0-rc3, so you
should be good. If not for some reason, it looks like 22.1.0 should be
coming down the pipeline soon based on the llvm-toolchain repo:
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commits/22
and there is always https://apt.llvm.org or the kernel.org copies if you
were really in a bind :)
Cheers,
Nathan
next prev parent reply other threads:[~2026-02-25 18:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 23:16 [PATCH] lib/Kconfig.debug: Require a release version of LLVM 22 for context analysis Nathan Chancellor
2026-02-25 7:00 ` Marco Elver
2026-02-25 14:52 ` Peter Zijlstra
2026-02-25 18:53 ` Nathan Chancellor [this message]
2026-02-25 22:23 ` Peter Zijlstra
2026-02-26 8:08 ` Sylvestre Ledru
2026-02-25 15:31 ` [tip: locking/urgent] " tip-bot2 for Nathan Chancellor
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=20260225185357.GA2755225@ax162 \
--to=nathan@kernel.org \
--cc=bvanassche@acm.org \
--cc=elver@google.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=peterz@infradead.org \
--cc=pkg-llvm-team@lists.alioth.debian.org \
/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