From: Nathan Chancellor <nathan@kernel.org>
To: Nicolas Schier <nsc@kernel.org>, Kees Cook <kees@kernel.org>,
Julian Braha <julianbraha@gmail.com>,
Lorenzo Stoakes <ljs@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] scripts/Kconfig.toolchain: Drop compiler symbols from dependencies
Date: Fri, 9 Oct 2026 21:22:57 +0200 [thread overview]
Message-ID: <20261009192257.GC757048@ax162> (raw)
In-Reply-To: <asiorcpffrSJ6_cM@derry.ads.avm.de>
On Fri, Oct 09, 2026 at 10:41:17AM +0200, Nicolas Schier wrote:
> On Thu, Oct 08, 2026 at 11:54:30PM -0700, Kees Cook wrote:
> > Hm, does this mean we're running more probes at start-up now compared to
> > before (since the Makefile idef would have suppressed them)?
>
> Yes, probing compiler flags via Kconfig results in more
> useless probing calls. That's unfortunate, but the move to Kconfig look
> still reasonable to me due.
Right, we probe in more cases when we have to but the trade off is that
we shouldn't have to in the common case of incremental compiles with the
same toolchain.
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-10-09 19:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 15:22 [PATCH 0/2] Initial ergonomic improvements to scripts/Kconfig.toolchain Nathan Chancellor
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-09 19:22 ` Nathan Chancellor [this message]
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
2026-10-09 19:14 ` Nathan Chancellor
2026-10-09 19:43 ` Nicolas Schier
2026-10-09 20:27 ` 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=20261009192257.GC757048@ax162 \
--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®