From: Nathan Chancellor <nathan@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>,
Julian Braha <julianbraha@gmail.com>
Cc: Lorenzo Stoakes <ljs@kernel.org>, Kees Cook <kees@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Initial ergonomic improvements to scripts/Kconfig.toolchain
Date: Wed, 07 Oct 2026 17:22:20 +0200 [thread overview]
Message-ID: <20261007-scripts-kconfig-toolchain-improvements-v1-0-1e524178da11@kernel.org> (raw)
Hi all,
This series includes a cleanup to scripts/Kconfig.toolchain around
dependencies (the first patch) and improves the ergonomics of using
cc-option and cc-option-str in Kconfig to disable warnings, making
Kconfig and Kbuild more unified in their behavior (the second patch).
---
Nathan Chancellor (2):
scripts/Kconfig.toolchain: Drop compiler symbols from dependencies
kconfig: Improve ergonomics around disabling warnings with cc-option
scripts/Kconfig.include | 2 +-
scripts/Kconfig.toolchain | 22 +++++++++++-----------
2 files changed, 12 insertions(+), 12 deletions(-)
---
base-commit: a98db7418797bc27bef53c861b97ac748f598414
change-id: 20261007-scripts-kconfig-toolchain-improvements-2e5f023ba136
Best regards,
--
Cheers,
Nathan
next reply other threads:[~2026-10-07 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 15:22 Nathan Chancellor [this message]
2026-10-07 15:22 ` [PATCH 1/2] scripts/Kconfig.toolchain: Drop compiler symbols from dependencies Nathan Chancellor
2026-10-09 6:54 ` Kees Cook
2026-10-09 8:41 ` Nicolas Schier
2026-10-07 15:22 ` [PATCH 2/2] kconfig: Improve ergonomics around disabling warnings with cc-option Nathan Chancellor
2026-10-09 6:54 ` Kees Cook
2026-10-07 16:48 ` [PATCH 0/2] Initial ergonomic improvements to scripts/Kconfig.toolchain Nicolas Schier
2026-10-09 6:56 ` Kees Cook
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=20261007-scripts-kconfig-toolchain-improvements-v1-0-1e524178da11@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=ljs@kernel.org \
--cc=nsc@kernel.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®