From: Nathan Chancellor <nathan@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: "Nicolas Schier" <nsc@kernel.org>,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
"Julian Braha" <julianbraha@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Vegard Nossum" <vegard.nossum@oracle.com>,
"Nauman Sabir" <officialnaumansabir@gmail.com>,
"Tejun Heo" <tj@kernel.org>, "Nicolas Pitre" <nico@fluxnic.net>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Matthew Maurer" <mmaurer@google.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Andrew Jones" <andrew.jones@linux.dev>,
"Graham Roff" <grahamr@qti.qualcomm.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
"Gary Guo" <gary@garyguo.net>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-doc@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH 0/3] kconfig: Introduce cc-option-str
Date: Fri, 18 Sep 2026 18:25:08 -0700 [thread overview]
Message-ID: <20260919012508.GA3573999@ax162> (raw)
In-Reply-To: <20260919005923.i.879-kees@kernel.org>
On Fri, Sep 18, 2026 at 05:59:24PM -0700, Kees Cook wrote:
> Hi,
>
> While reviewing the recent build speedup series[1], it became clear
> that we needed a general solution in kconfig to avoid repeating detected
> toolchain options. Implement cc-option-str and ld-option-str, and while
> at it, create "def_string" and friends to match "def_bool".
>
> -Kees
>
> [1] https://lore.kernel.org/all/20260918054058.GA384222@ax162/
>
> Kees Cook (3):
> kconfig: Add "def_string", "def_int" and "def_hex"
> kconfig: Replace "cc-option-bit" with "cc-option-str"
> kconfig: Add "ld-option-str"
Thanks, exactly what I had in mind. This seems reasonable to me and
passes my basic testing. I will let folks chime in for a few days then
apply this to kbuild-next so that Lorenzo can use it as part of the
speed up series.
--
Cheers,
Nathan
prev parent reply other threads:[~2026-09-19 1:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 0:59 Kees Cook
2026-09-19 0:59 ` [PATCH 1/3] kconfig: Add "def_string", "def_int" and "def_hex" Kees Cook
2026-09-19 0:59 ` [PATCH 2/3] kconfig: Replace "cc-option-bit" with "cc-option-str" Kees Cook
2026-09-19 0:59 ` [PATCH 3/3] kconfig: Add "ld-option-str" Kees Cook
2026-09-19 1:25 ` Nathan Chancellor [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=20260919012508.GA3573999@ax162 \
--to=nathan@kernel.org \
--cc=andrew.jones@linux.dev \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=gary@garyguo.net \
--cc=grahamr@qti.qualcomm.com \
--cc=julianbraha@gmail.com \
--cc=kees@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=masahiroy@kernel.org \
--cc=mmaurer@google.com \
--cc=nico@fluxnic.net \
--cc=nsc@kernel.org \
--cc=officialnaumansabir@gmail.com \
--cc=ojeda@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=tj@kernel.org \
--cc=vegard.nossum@oracle.com \
/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®