From: Nicolas Schier <nsc@kernel.org>
To: "Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Thomas Weißschuh" <linux@weissschuh.net>
Cc: Nicolas Schier <nsc@kernel.org>,
llvm@lists.linux.dev, linux-kbuild@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] kbuild: Follow-up to "Reject unexpected values for LLVM="
Date: Tue, 3 Mar 2026 17:48:00 +0100 [thread overview]
Message-ID: <177255616155.3889155.9191147372307170498.b4-ty@kernel.org> (raw)
In-Reply-To: <20260226-kbuild-llvm-followup-v1-0-201cc2a492d9@weissschuh.net>
On Thu, 26 Feb 2026 22:23:56 +0100, Thomas Weißschuh wrote:
> Some cleanups.
>
>
Applied to kbuild/linux.git (kbuild-for-next), thanks!
[1/2] Documentation/llvm: drop note about LLVM=0
https://git.kernel.org/kbuild/c/8830b2e5
[2/2] tools/build: Reject unexpected values for LLVM=
https://git.kernel.org/kbuild/c/7239ae53
Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped,
reverted or modified (e.g. trailers). Patches applied to a
kbuild-*-unstable branch are accepted pending wider testing in
linux-next and any post-commit review; they will generally be moved
to the main branch (kbuild-next or kbuild-fixes) in a week if no
issues are found.
Best regards,
--
Nicolas
prev parent reply other threads:[~2026-03-03 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 21:23 Thomas Weißschuh
2026-02-26 21:23 ` [PATCH 1/2] Documentation/llvm: drop note about LLVM=0 Thomas Weißschuh
2026-02-26 21:43 ` Nathan Chancellor
2026-02-27 8:10 ` Nicolas Schier
2026-02-26 21:23 ` [PATCH 2/2] tools/build: Reject unexpected values for LLVM= Thomas Weißschuh
2026-02-26 21:45 ` Nathan Chancellor
2026-02-27 8:08 ` Nicolas Schier
2026-03-03 16:48 ` Nicolas Schier [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=177255616155.3889155.9191147372307170498.b4-ty@kernel.org \
--to=nsc@kernel.org \
--cc=corbet@lwn.net \
--cc=justinstitt@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®