From: Nathan Chancellor <nathan@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Julian Braha <julianbraha@gmail.com>,
akpm@linux-foundation.org, ljs@kernel.org, arnd@arndb.de,
gregkh@linuxfoundation.org, masahiroy@kernel.org, nsc@kernel.org,
ojeda@kernel.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] scripts: add kconfirm
Date: Tue, 28 Apr 2026 14:31:01 -0400 [thread overview]
Message-ID: <20260428183101.GA3304253@ax162> (raw)
In-Reply-To: <87mrynmuuu.fsf@trenco.lwn.net>
On Tue, Apr 28, 2026 at 01:01:29AM -0600, Jonathan Corbet wrote:
> Also, a nit, but I would really suggest putting it under tools/ rather
> than in the scripts/ dumping ground.
As if tools/ isn't its own dumping ground? :)
While I can understand the desire to avoid adding more random stuff to
scripts/, it sets a confusing precedent because tools/ is not a part of
Kbuild, so I would not expect tools that would run within Kbuild to live
there (which this one appears to do). While there are obvious exceptions
such as objtool and resolve_btfids, I would like to avoid adding new
ones, which aligns with the comment added by Masahiro's commit
6e6ef2da3a28 ("Makefile: add comment to discourage tools/* addition for
kernel builds"). Maybe this could be mitigated with a tools/kbuild/
directory or something but not sure. Just some additional input.
Cheers,
Nathan
next prev parent reply other threads:[~2026-04-28 18:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 17:44 [RFC PATCH 0/2] scripts: add kconfirm Julian Braha
2026-04-27 17:44 ` [RFC PATCH 1/2] " Julian Braha
2026-04-27 20:48 ` Greg KH
2026-04-28 7:01 ` Jonathan Corbet
2026-04-28 18:31 ` Nathan Chancellor [this message]
2026-04-28 19:08 ` Jonathan Corbet
2026-04-27 17:44 ` [RFC PATCH 2/2] Documentation: dev-tools: " Julian Braha
2026-04-27 18:17 ` Miguel Ojeda
2026-04-27 19:33 ` Arnd Bergmann
2026-04-28 11:51 ` Miguel Ojeda
2026-04-28 12:58 ` Gary Guo
2026-04-28 18:45 ` Nathan Chancellor
2026-04-28 17:01 ` Julian Braha
2026-04-28 8:23 ` Jani Nikula
2026-04-28 18:06 ` Julian Braha
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=20260428183101.GA3304253@ax162 \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=julianbraha@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=masahiroy@kernel.org \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.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