Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Conor Dooley <conor@kernel.org>, <soc@kernel.org>,
	Claudiu Beznea <Claudiu.Beznea@microchip.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Lars Povlsen <lars.povlsen@microchip.com>,
	Steen Hegelund <Steen.Hegelund@microchip.com>,
	Daniel Machon <daniel.machon@microchip.com>
Subject: Re: [PATCH v1] MAINTAINERS: update arm64 Microchip entries
Date: Mon, 22 May 2023 09:52:31 +0200	[thread overview]
Message-ID: <5e0a2144-81fc-8e83-f8e5-f88abfbf5809@microchip.com> (raw)
In-Reply-To: <20230517-shimmer-retry-34596c637882@spud>

On 17/05/2023 at 17:55, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
> 
> Krzysztof noticed that patches for arch/arm64/boot/dts/microchip were
> getting lost & the listed tree was inactive.
> 
> Nicolas and I are willing to shepherd patches to Arnd, using the
> existing at91 tree, so add a new entry covering
> arch/arm64/boot/dts/microchip, listing us as maintainers.

Yes, and I would like that Claudiu is part of this as well as he very 
active in reviews and is building most of the pull-requests for at91.

Thanks for helping clarifying this.
Best regards,
   Nicolas

> Drop the tree from the existing sparx5 entry & narrow the devicetree
> pattern to just sparx devices, leaving Lars, Steen and Daniel looking
> after support for their SoCs.
> 
> CC: Rob Herring <robh+dt@kernel.org>
> CC: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
> CC: Conor Dooley <conor@kernel.org>
> CC: Nicolas Ferre <nicolas.ferre@microchip.com>
> CC: soc@kernel.org
> CC: Lars Povlsen <lars.povlsen@microchip.com>
> CC: Steen Hegelund <Steen.Hegelund@microchip.com>
> CC: Daniel Machon <daniel.machon@microchip.com>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
>   MAINTAINERS | 11 +++++++++--
>   1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7e0b87d5aa2e..b5c10fb8ae49 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2434,6 +2434,14 @@ X:       drivers/net/wireless/atmel/
>   N:     at91
>   N:     atmel
> 
> +ARM/MICROCHIP (ARM64) SoC support
> +M:     Conor Dooley <conor@kernel.org>
> +M:     Nicolas Ferre <nicolas.ferre@microchip.com>
> +L:     linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> +S:     Supported
> +T:     git https://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git
> +F:     arch/arm64/boot/dts/microchip/
> +
>   ARM/Microchip Sparx5 SoC support
>   M:     Lars Povlsen <lars.povlsen@microchip.com>
>   M:     Steen Hegelund <Steen.Hegelund@microchip.com>
> @@ -2441,8 +2449,7 @@ M:        Daniel Machon <daniel.machon@microchip.com>
>   M:     UNGLinuxDriver@microchip.com
>   L:     linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
>   S:     Supported
> -T:     git git://github.com/microchip-ung/linux-upstream.git
> -F:     arch/arm64/boot/dts/microchip/
> +F:     arch/arm64/boot/dts/microchip/sparx*
>   F:     drivers/net/ethernet/microchip/vcap/
>   F:     drivers/pinctrl/pinctrl-microchip-sgpio.c
>   N:     sparx5
> --
> 2.39.2
> 

-- 
Nicolas Ferre


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-05-22  7:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 15:55 [PATCH v1] MAINTAINERS: update arm64 Microchip entries Conor Dooley
2023-05-22  7:52 ` Nicolas Ferre [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=5e0a2144-81fc-8e83-f8e5-f88abfbf5809@microchip.com \
    --to=nicolas.ferre@microchip.com \
    --cc=Claudiu.Beznea@microchip.com \
    --cc=Steen.Hegelund@microchip.com \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=daniel.machon@microchip.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars.povlsen@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=soc@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