From: Nathan Chancellor <nathan@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>, Nicolas Schier <nsc@kernel.org>
Cc: Julian Braha <julianbraha@gmail.com>,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
Kees Cook <kees@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Ricardo Ribalda <ribalda@chromium.org>,
linux-s390@vger.kernel.org
Subject: [PATCH 0/2] kbuild: Fallout from moving '-mfentry' check into Kconfig stage
Date: Tue, 20 Oct 2026 14:52:17 -0700 [thread overview]
Message-ID: <20261020-kconfig-fix-mfentry-check-v1-0-428258bc0fc0@kernel.org> (raw)
Hi all,
Ricardo reported an issue from moving the compiler test for '-mfentry'
into Kconfig. In testing that patch, I noticed that the kernel.org GCC
builds for s390 were not probing correctly for '-mfentry' support.
The first patch moves the check for '-mfentry' back into Kbuild where we
have the proper information for whether this flag is actually supported.
The second patch documents the reasons for these issues for future
travelers to hopefully avoid these problems.
I plan to take this via kbuild-fixes after sufficient review/comments.
---
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(-)
---
base-commit: 997208ce9f43f01febac956cf9aeffe89945e3c1
change-id: 20261020-kconfig-fix-mfentry-check-50525bc5a6ca
Best regards,
--
Cheers,
Nathan
next reply other threads:[~2026-10-20 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 21:52 Nathan Chancellor [this message]
2026-10-20 21:52 ` [PATCH 1/2] kbuild: Move testing of '-mfentry' back to Makefile from Kconfig Nathan Chancellor
2026-10-20 21:52 ` [PATCH 2/2] scripts/Kconfig.toolchain: Highlight cc-option differences between Kconfig and Kbuild 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=20261020-kconfig-fix-mfentry-check-v1-0-428258bc0fc0@kernel.org \
--to=nathan@kernel.org \
--cc=julianbraha@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=nsc@kernel.org \
--cc=ribalda@chromium.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®