public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Julian Braha <julianbraha@gmail.com>,
	akpm@linux-foundation.org, ljs@kernel.org
Cc: arnd@arndb.de, gregkh@linuxfoundation.org, masahiroy@kernel.org,
	nathan@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,
	Julian Braha <julianbraha@gmail.com>
Subject: Re: [RFC PATCH 1/2] scripts: add kconfirm
Date: Tue, 28 Apr 2026 01:01:29 -0600	[thread overview]
Message-ID: <87mrynmuuu.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260427174429.779474-2-julianbraha@gmail.com>

Julian Braha <julianbraha@gmail.com> writes:

> Add kconfirm into scripts/ and modify the root Makefile and
> scripts/Makefile accordingly so that it can be compiled and run with:
> `make kconfirm`
> from the root of the tree.

As Greg noted, it would be helpful if you said what this tool does in
the changelog.

Also, a nit, but I would really suggest putting it under tools/ rather
than in the scripts/ dumping ground.

Thanks,

jon

  parent reply	other threads:[~2026-04-28  7:01 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 [this message]
2026-04-28 18:31     ` Nathan Chancellor
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=87mrynmuuu.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --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=nathan@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