From: Nathan Chancellor <nathan@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Nicolas Schier <nsc@kernel.org>,
linux-kbuild@vger.kernel.org
Subject: [GIT PULL] Kbuild updates for 7.2 #2
Date: Wed, 24 Jun 2026 15:57:11 -0700 [thread overview]
Message-ID: <20260624225711.GA1132314@ax162> (raw)
Hi Linus,
Please pull this second round of Kbuild changes for 7.2. It has all been
in next for at least a few cycles. If there are any problems, please let
me know.
Cheers,
Nathan
The following changes since commit 1a1e62a5a48494cdf33e3bfb82fb8f408da7c4cc:
kconfig: tests: fix typo in comment (2026-06-09 16:28:46 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git tags/kbuild-7.2-2
for you to fetch changes up to 645323a7f4e55bb3abb0cb003b6b9dc715c8dc21:
kconfig: add optional warnings for changed input values (2026-06-18 11:46:32 -0700)
----------------------------------------------------------------
Second round of Kbuild changes for 7.2
- Link host programs with ld.lld when $(LLVM) is set to match user's
expectations that LLVM will be used exclusively during the build
process
- Fix modpost warnings from static variable name promotion that can
happen more aggressively with the recently merged distributed ThinLTO
support
- Add an optional warning for user-supplied Kconfig values that changed
after processing, such as out of range values or options that have
incorrect / missing dependencies
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
----------------------------------------------------------------
Nathan Chancellor (1):
kbuild: Use ld.lld for linking host programs when LLVM is set
Pengpeng Hou (1):
kconfig: add optional warnings for changed input values
Rong Xu (1):
modpost: Ignore Clang LTO suffixes in symbol matching
Documentation/kbuild/kconfig.rst | 5 +
Makefile | 3 +
scripts/kconfig/confdata.c | 106 ++++++++++++++++++++-
scripts/kconfig/tests/conftest.py | 8 +-
scripts/kconfig/tests/warn_changed_input/Kconfig | 40 ++++++++
.../kconfig/tests/warn_changed_input/__init__.py | 33 +++++++
scripts/kconfig/tests/warn_changed_input/config | 3 +
.../tests/warn_changed_input/expected_config | 6 ++
.../tests/warn_changed_input/expected_defconfig | 1 +
.../tests/warn_changed_input/expected_stderr | 4 +
scripts/mod/modpost.c | 2 +-
11 files changed, 204 insertions(+), 7 deletions(-)
create mode 100644 scripts/kconfig/tests/warn_changed_input/Kconfig
create mode 100644 scripts/kconfig/tests/warn_changed_input/__init__.py
create mode 100644 scripts/kconfig/tests/warn_changed_input/config
create mode 100644 scripts/kconfig/tests/warn_changed_input/expected_config
create mode 100644 scripts/kconfig/tests/warn_changed_input/expected_defconfig
create mode 100644 scripts/kconfig/tests/warn_changed_input/expected_stderr
reply other threads:[~2026-06-24 22:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260624225711.GA1132314@ax162 \
--to=nathan@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsc@kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.