From: Julian Braha <julianbraha@gmail.com>
To: nathan@kernel.org, nsc@kernel.org
Cc: ojeda@kernel.org, akpm@linux-foundation.org,
jani.nikula@linux.intel.com, gary@garyguo.net,
gregkh@linuxfoundation.org, arnd@arndb.de, ljs@kernel.org,
andrew.jones@linux.dev, masahiroy@kernel.org, corbet@lwn.net,
qingfang.deng@linux.dev, demiobenour@gmail.com, ej@inai.de,
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: [PATCH v4 5/5] MAINTAINERS: add entry for kconfirm
Date: Mon, 27 Jul 2026 01:16:23 +0100 [thread overview]
Message-ID: <20260727001623.2794156-6-julianbraha@gmail.com> (raw)
In-Reply-To: <20260727001623.2794156-1-julianbraha@gmail.com>
I will maintain all files introduced with kconfirm.
Signed-off-by: Julian Braha <julianbraha@gmail.com>
---
MAINTAINERS | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index cc3c01eecfa2..c7066ccef6c9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14041,6 +14041,13 @@ F: Documentation/kbuild/kconfig*
F: scripts/Kconfig.include
F: scripts/kconfig/
+KCONFIRM AND KCONFIG BINDINGS [RUST]
+M: Julian Braha <julianbraha@gmail.com>
+S: Maintained
+F: Documentation/dev-tools/kconfirm.rst
+F: scripts/kconfig/kconfig.rs
+F: scripts/kconfig/kconfirm/
+
KCORE
M: Omar Sandoval <osandov@osandov.com>
L: linux-debuggers@vger.kernel.org
--
2.54.0
prev parent reply other threads:[~2026-07-27 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 0:16 [PATCH v4 0/5] add kconfirm Julian Braha
2026-07-27 0:16 ` [PATCH v4 1/5] kconfig: add add another callback to the parser to view raw parse tree Julian Braha
2026-07-27 0:16 ` [PATCH 2/5] kconfig: add kconfirm Julian Braha
2026-07-27 0:16 ` [PATCH v4 3/5] kconfirm: add tests Julian Braha
2026-07-27 0:16 ` [PATCH v4 4/5] Documentation: add kconfirm Julian Braha
2026-07-27 0:16 ` Julian Braha [this message]
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=20260727001623.2794156-6-julianbraha@gmail.com \
--to=julianbraha@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.jones@linux.dev \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=demiobenour@gmail.com \
--cc=ej@inai.de \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@linux.intel.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=qingfang.deng@linux.dev \
--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