From: Yixun Lan <dlan@gentoo.org>
To: Yangtao Li <frank.li@vivo.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Jisheng Zhang <jszhang@kernel.org>,
Icenowy Zheng <uwu@icenowy.me>, Wei Fu <wefu@redhat.com>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 5/5] MAINTAINERS: add entry for T-HEAD RISC-V SoC
Date: Thu, 11 May 2023 08:54:19 +0800 [thread overview]
Message-ID: <ZFw8u9uqaRvCEQCI@ofant> (raw)
In-Reply-To: <20230510204456.57202-5-frank.li@vivo.com>
Hi Yangtao:
On 04:44 Thu 11 May , Yangtao Li wrote:
> From: Jisheng Zhang <jszhang@kernel.org>
>
> Jisheng:
> I would like to temporarily maintain the T-HEAD RISC-V SoC support.
>
> Yangtao:
> Wei and me would like to help support and maintain too.
>
> Cc: Icenowy Zheng <uwu@icenowy.me>
> Cc: Wei Fu <wefu@redhat.com>
> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
> v2:
> -add Yangtao and Wei
> MAINTAINERS | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7e0b87d5aa2e..592769efd1d1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18155,6 +18155,14 @@ T: git https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/
> F: Documentation/devicetree/bindings/riscv/
> F: arch/riscv/boot/dts/
>
> +RISC-V T-HEAD SoC SUPPORT
> +M: Jisheng Zhang <jszhang@kernel.org>
> +M: Wei Fu <wefu@redhat.com>
> +M: Yangtao Li <frank.li@vivo.com>
> +L: linux-riscv@lists.infradead.org
> +S: Maintained
> +F: arch/riscv/boot/dts/thead/
> +
> RNBD BLOCK DRIVERS
> M: Md. Haris Iqbal <haris.iqbal@ionos.com>
> M: Jack Wang <jinpu.wang@ionos.com>
> --
> 2.34.1
>
Don't get yourself wrong, no objection personally..
But as I saw, none of contributors has affinity with T-Head, so no idea how this will
work well.. always better to take over maintainership after show enough commitment..
Anyway, raise your comments, and I'd more than happy to be proved I'm wrong
--
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55
next prev parent reply other threads:[~2023-05-11 0:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 20:44 [PATCH v2 1/5] riscv: Add the T-HEAD SoC family Kconfig option Yangtao Li
2023-05-10 20:44 ` [PATCH v2 2/5] riscv: dts: add initial T-HEAD light SoC device tree Yangtao Li
2023-05-11 0:35 ` Yixun Lan
2023-05-11 0:39 ` Jisheng Zhang
2023-05-11 9:05 ` Krzysztof Kozlowski
2023-05-10 20:44 ` [PATCH v2 3/5] riscv: dts: thead: add sipeed Lichee Pi 4A board " Yangtao Li
2023-05-11 0:42 ` Yixun Lan
2023-05-11 9:12 ` Krzysztof Kozlowski
2023-05-10 20:44 ` [PATCH v2 4/5] riscv: defconfig: Enable the T-HEAD SoC Yangtao Li
2023-05-10 20:44 ` [PATCH v2 5/5] MAINTAINERS: add entry for T-HEAD RISC-V SoC Yangtao Li
2023-05-10 20:52 ` Conor Dooley
2023-05-11 0:54 ` Yixun Lan [this message]
2023-05-11 5:20 ` Conor Dooley
2023-05-10 23:49 ` [PATCH v2 1/5] riscv: Add the T-HEAD SoC family Kconfig option Yixun Lan
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=ZFw8u9uqaRvCEQCI@ofant \
--to=dlan@gentoo.org \
--cc=aou@eecs.berkeley.edu \
--cc=frank.li@vivo.com \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=uwu@icenowy.me \
--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