From: Nicolas Schier <nicolas@fjasle.eu>
To: Nathan Chancellor <nathan@kernel.org>
Cc: masahiroy@kernel.org, ndesaulniers@google.com, morbo@google.com,
justinstitt@google.com, linux-kbuild@vger.kernel.org,
llvm@lists.linux.dev, patches@lists.linux.dev
Subject: Re: [PATCH] MAINTAINERS: Add scripts/clang-tools to Kbuild section
Date: Fri, 8 Dec 2023 14:20:39 +0100 [thread overview]
Message-ID: <ZXMYJ6JCm3ZmDJ9G@fjasle.eu> (raw)
In-Reply-To: <20231205-maintainers-kbuild-clang-tools-v1-1-a646a1985300@kernel.org>
On Tue, Dec 05, 2023 at 10:05:57AM -0700 Nathan Chancellor wrote:
> Masahiro has always applied scripts/clang-tools patches but it is not
> included in the Kbuild section, so neither he nor linux-kbuild get cc'd
> on patches that touch those files.
>
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 788be9ab5b73..cd9bf44dc1b3 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11526,6 +11526,7 @@ F: scripts/*vmlinux*
> F: scripts/Kbuild*
> F: scripts/Makefile*
> F: scripts/basic/
> +F: scripts/clang-tools/
> F: scripts/dummy-tools/
> F: scripts/mk*
> F: scripts/mod/
>
> ---
> base-commit: 33cc938e65a98f1d29d0a18403dbbee050dcad9a
> change-id: 20231205-maintainers-kbuild-clang-tools-93666b423b02
>
> Best regards,
> --
> Nathan Chancellor <nathan@kernel.org>
Thanks, sounds reasonable to me.
Acked-by: Nicolas Schier <nicolas@fjasle.eu>
next prev parent reply other threads:[~2023-12-08 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 17:05 [PATCH] MAINTAINERS: Add scripts/clang-tools to Kbuild section Nathan Chancellor
2023-12-08 13:20 ` Nicolas Schier [this message]
2023-12-10 6:38 ` 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=ZXMYJ6JCm3ZmDJ9G@fjasle.eu \
--to=nicolas@fjasle.eu \
--cc=justinstitt@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=patches@lists.linux.dev \
/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