From: Nicolas Schier <nicolas@fjasle.eu>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/2] MAINTAINERS: Add kconfig utility scripts
Date: Wed, 15 Jan 2025 13:11:06 +0100 [thread overview]
Message-ID: <Z4el2qEV1xZIMBfk@bergen> (raw)
In-Reply-To: <20250108-diffconfig-validate-v1-1-4b3d8ee489da@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
On Wed 08 Jan 2025 13:34:28 GMT, Thomas Weißschuh wrote:
> 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
Thanks!
Does it make sense to add scripts/extract-ikconfig also? It does not
handle kconfig language at all, but linux-kbuild would probably still a
good place for review.
Nevertheless,
Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
Kind regards,
Nicolas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-01-15 12:32 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 ` [PATCH 1/2] MAINTAINERS: Add kconfig utility scripts Thomas Weißschuh
2025-01-15 12:11 ` Nicolas Schier [this message]
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=Z4el2qEV1xZIMBfk@bergen \
--to=nicolas@fjasle.eu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.