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 fixes for 7.4 #1
Date: Fri, 30 Oct 2026 12:25:17 -0700 [thread overview]
Message-ID: <20261030192517.GA49624@ax162> (raw)
Hi Linus,
Please pull this small set of fixes for 7.4-rc1.
Cheers,
Nathan
The following changes since commit 997208ce9f43f01febac956cf9aeffe89945e3c1:
Merge branch 'kbuild-next-speedups' into kbuild-next (2026-10-17 15:20:23 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git tags/kbuild-fixes-7.4-1
for you to fetch changes up to e58096244338308dde3fa76982c8042981ddda52:
scripts/Kconfig.toolchain: Highlight cc-option differences between Kconfig and Kbuild (2026-10-20 14:55:40 -0700)
----------------------------------------------------------------
First round of Kbuild fixes for 7.4
- Move probing of '-mfentry' back into Makefile instead of Kconfig
because it does not interact well with toolchains that support
multiple bit widths
- Add a big comment in scripts/Kconfig.toolchain of two pitfalls when
moving cc-option checks from Kbuild to Kconfig
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
----------------------------------------------------------------
Nathan Chancellor (2):
kbuild: Move testing of '-mfentry' back to Makefile from Kconfig
scripts/Kconfig.toolchain: Highlight cc-option differences between Kconfig and Kbuild
Makefile | 3 ++-
scripts/Kconfig.toolchain | 23 +++++++++++++++++++----
2 files changed, 21 insertions(+), 5 deletions(-)
next reply other threads:[~2026-10-30 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 19:25 Nathan Chancellor [this message]
2026-10-31 0:19 ` [GIT PULL] Kbuild fixes for 7.4 #1 pr-tracker-bot
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=20261030192517.GA49624@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox