From: Julian Braha <julianbraha@gmail.com>
To: nathan@kernel.org, nsc@kernel.org
Cc: andi@firstfloor.org, ljs@kernel.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Julian Braha <julianbraha@gmail.com>
Subject: [PATCH] MAINTAINERS: cleanup Kconfig entry
Date: Thu, 12 Nov 2026 16:48:26 +0000 [thread overview]
Message-ID: <20261112164826.110736-1-julianbraha@gmail.com> (raw)
'scripts/config' provides a CLI for kernel configuration, but currently is
not included in any MAINTAINERS entry, despite the commit that created it
using the 'kconfig:' subject:
commit 8e54701ea85b ("kconfig: add script to manipulate .config files on the command line")
so let's add it to the Kconfig entry.
Additionally, 'scripts/Kconfig.toolchain' is used for checking various
aspects of the active build toolchain from the host environment. It's
merely written in Kconfig, and is not really part of Kconfig's
implementation. Let's move it into the Kbuild entry.
Signed-off-by: Julian Braha <julianbraha@gmail.com>
---
MAINTAINERS | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 93abbb315065..245bbfed8122 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14374,8 +14374,8 @@ S: Odd Fixes
Q: https://patchwork.kernel.org/project/linux-kbuild/list/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git
F: Documentation/kbuild/kconfig*
+F: scripts/config
F: scripts/Kconfig.include
-F: scripts/Kconfig.toolchain
F: scripts/kconfig/
KCORE
@@ -14451,6 +14451,7 @@ F: Documentation/kbuild/
F: Makefile
F: scripts/*vmlinux*
F: scripts/Kbuild*
+F: scripts/Kconfig.toolchain
F: scripts/Makefile*
F: scripts/bash-completion/
F: scripts/basic/
--
2.56.0
next reply other threads:[~2026-11-12 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 16:48 Julian Braha [this message]
2026-11-12 16:59 ` Lorenzo Stoakes (ARM)
2026-11-12 17:17 ` 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=20261112164826.110736-1-julianbraha@gmail.com \
--to=julianbraha@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=nathan@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®