public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: [PATCH 1/2] MAINTAINERS: Add kconfig utility scripts
Date: Wed, 08 Jan 2025 13:34:28 +0100	[thread overview]
Message-ID: <20250108-diffconfig-validate-v1-1-4b3d8ee489da@linutronix.de> (raw)
In-Reply-To: <20250108-diffconfig-validate-v1-0-4b3d8ee489da@linutronix.de>

There are various utilities in scripts/ which work with kconfig files.
These have currently no maintainer.
As most patches for them are applied through kconfig/kbuild anyways,
add an explicit maintainership entry.

Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
---
 MAINTAINERS | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 30cbc3d44cd53e6b1a81d56161004d7ab825d7a9..2bd414fb3e6d6515b57a57a5f3d4d735137edcce 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12385,6 +12385,9 @@ Q:	https://patchwork.kernel.org/project/linux-kbuild/list/
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git kbuild
 F:	Documentation/kbuild/kconfig*
 F:	scripts/Kconfig.include
+F:	scripts/checkkconfigsymbols.py
+F:	scripts/config
+F:	scripts/diffconfig
 F:	scripts/kconfig/
 
 KCOV

-- 
2.47.1


  reply	other threads:[~2025-01-08 12:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 12:34 [PATCH 0/2] diffconfig: add verification mode Thomas Weißschuh
2025-01-08 12:34 ` Thomas Weißschuh [this message]
2025-01-15 12:11   ` [PATCH 1/2] MAINTAINERS: Add kconfig utility scripts Nicolas Schier
2025-01-15 12:26     ` Thomas Weißschuh
2025-02-10  5:23   ` Masahiro Yamada
2025-02-10 10:35     ` Thomas Weißschuh
2025-01-08 12:34 ` [PATCH 2/2] diffconfig: add verification mode Thomas Weißschuh
2025-01-15 12:35   ` Nicolas Schier
2025-02-10  5:23   ` Masahiro Yamada

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=20250108-diffconfig-validate-v1-1-4b3d8ee489da@linutronix.de \
    --to=thomas.weissschuh@linutronix.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@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