devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@kernel.org>
To: Drew Fustini <dfustini@baylibre.com>
Cc: Guo Ren <guoren@kernel.org>, Fu Wei <wefu@redhat.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Conor Dooley <conor@kernel.org>,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Robert Nelson <robertcnelson@beagleboard.org>,
	Jason Kridner <jkridner@beagleboard.org>
Subject: Re: [PATCH v2 3/3] MAINTAINERS: add reviewer for T-Head RISC-V SoC support
Date: Wed, 26 Jul 2023 08:18:50 +0800	[thread overview]
Message-ID: <ZMBmalZwaRCiy2BG@xhacker> (raw)
In-Reply-To: <20230722-upstream-beaglev-ahead-dts-v2-3-a470ab8fe806@baylibre.com>

On Mon, Jul 24, 2023 at 10:20:40AM -0700, Drew Fustini wrote:
> I will maintain support for the TH1520-based BeagleV Ahead board so
> adding myself as a reviewer for T-Head SoC patches.

Hi Drew,

Thanks for your interest in maintaining the SoC support part. However,
maintainership involves active reviewing and maintaining the whole SoC
support part and not just specific board part, although currently, the
SoC support in mainline is minimal. I'd like to see your patch
reviewing, testing and so on.

Thanks
> 
> Acked-by: Guo Ren <guoren@kernel.org>
> Signed-off-by: Drew Fustini <dfustini@baylibre.com>
> ---
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d516295978a4..eaec3333f2ed 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18326,6 +18326,7 @@ RISC-V THEAD SoC SUPPORT
>  M:	Jisheng Zhang <jszhang@kernel.org>
>  M:	Guo Ren <guoren@kernel.org>
>  M:	Fu Wei <wefu@redhat.com>
> +R:	Drew Fustini <dfustini@baylibre.com>
>  L:	linux-riscv@lists.infradead.org
>  S:	Maintained
>  F:	arch/riscv/boot/dts/thead/
> 
> -- 
> 2.34.1
> 

  reply	other threads:[~2023-07-26  0:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24 17:20 [PATCH v2 0/3] riscv: Add BeagleV Ahead board support Drew Fustini
2023-07-24 17:20 ` [PATCH v2 1/3] dt-bindings: riscv: Add BeagleV Ahead board compatibles Drew Fustini
2023-07-24 17:20 ` [PATCH v2 2/3] riscv: dts: thead: add BeagleV Ahead board device tree Drew Fustini
2023-07-24 17:20 ` [PATCH v2 3/3] MAINTAINERS: add reviewer for T-Head RISC-V SoC support Drew Fustini
2023-07-26  0:18   ` Jisheng Zhang [this message]
2023-07-26  1:38     ` Drew Fustini
2023-07-26 18:39       ` Conor Dooley
2023-07-24 17:36 ` [PATCH v2 0/3] riscv: Add BeagleV Ahead board support Conor Dooley
2023-07-24 17:43   ` Drew Fustini
2023-08-11 17:49 ` Conor Dooley
2023-08-11 20:56   ` Drew Fustini

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=ZMBmalZwaRCiy2BG@xhacker \
    --to=jszhang@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dfustini@baylibre.com \
    --cc=guoren@kernel.org \
    --cc=jkridner@beagleboard.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robertcnelson@beagleboard.org \
    --cc=robh+dt@kernel.org \
    --cc=wefu@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).