From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: renesas: Add "renesas," file content pattern
Date: Fri, 17 Mar 2023 11:01:39 +0100 [thread overview]
Message-ID: <ZBQ6g1gxBD8vOpc1@oden.dyn.berto.se> (raw)
In-Reply-To: <c1be1e97c5457eade25b0eb5118196677cecfc08.1679039809.git.geert+renesas@glider.be>
Hi Geert,
Neat!
On 2023-03-17 08:59:00 +0100, Geert Uytterhoeven wrote:
> Add a keyword match pattern for the word "renesas," in files to the
> ARM/RISC-V/RENESAS ARCHITECTURE section. This make sure patches
> changing drivers that match against "renesas,<foo>" (as used mostly for
> Renesas on-SoC components) are CCed to the linux-renesas-soc mailing
> list.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> ---
> To be queued in renesas-devel for v6.4.
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index fc343041495b7015..281c6da85a4bdf5d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2655,6 +2655,7 @@ F: arch/arm64/configs/renesas_defconfig
> F: arch/riscv/boot/dts/renesas/
> F: drivers/soc/renesas/
> F: include/linux/soc/renesas/
> +K: \brenesas,
>
> ARM/RISCPC ARCHITECTURE
> M: Russell King <linux@armlinux.org.uk>
> --
> 2.34.1
>
--
Kind Regards,
Niklas Söderlund
prev parent reply other threads:[~2023-03-17 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 7:59 [PATCH] MAINTAINERS: renesas: Add "renesas," file content pattern Geert Uytterhoeven
2023-03-17 9:02 ` Wolfram Sang
2023-03-17 10:01 ` Niklas Söderlund [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=ZBQ6g1gxBD8vOpc1@oden.dyn.berto.se \
--to=niklas.soderlund@ragnatech.se \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=wsa+renesas@sang-engineering.com \
/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.