From: Yangyu Chen <cyy@cyyself.name>
To: Conor Dooley <conor@kernel.org>
Cc: Yixun Lan <dlan@gentoo.org>,
linux-riscv@lists.infradead.org,
Conor Dooley <conor+dt@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Samuel Holland <samuel.holland@sifive.com>,
Anup Patel <anup.patel@wdc.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jesse Taube <jesse@rivosinc.com>
Subject: Re: [PATCH v1 0/9] riscv: add initial support for SpacemiT K1
Date: Mon, 17 Jun 2024 10:00:32 +0800 [thread overview]
Message-ID: <tencent_2ABAC5E885F8354EF1F9084A6B5B398EE00A@qq.com> (raw)
In-Reply-To: <20240616224811.GC3983622@ofsar>
> On Jun 17, 2024, at 06:48, Yixun Lan <dlan@gentoo.org> wrote:
>
> Hi Conor
> Thanks for bringing this up
>
> On 19:35 Sun 16 Jun , Conor Dooley wrote:
>> On Mon, Jun 17, 2024 at 01:18:52AM +0800, Yangyu Chen wrote:
>>
>> No MAINTAINERS update, so I figure that means you don't want to maintain
>> it going forwards? If there's someone out that that does care about the
>> spacemit k1 (Jesse maybe?), then I'd be more than happy to have them
>> look after it.
Actually, I don’t know how to be a maintainer. Should I have to
provide a new git tree and all the new patches merged to my tree
and then submit a git pull? Or reuse the RISC-V mailing list and
just give a review, and the patches come to soc misc tree? I would
like the latter one.
> Yangyu kind of has limited time, too many stuff for him..
>
True. Maybe I can have a review and test the patch in one week.
However, providing a review and test in 2-3 days is sometimes hard
for me.
> I'd volunteered to help on this if it can fill the gap
> Also I'd be more than happy if anyone willing step forward to co-maintain..
>
Thanks. Really appreciate it.
Should I provide a diff like this:
diff --git a/MAINTAINERS b/MAINTAINERS
index d6c90161c7bf..718d30996f12 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19306,6 +19306,7 @@ F: arch/riscv/boot/dts/
X: arch/riscv/boot/dts/allwinner/
X: arch/riscv/boot/dts/renesas/
X: arch/riscv/boot/dts/sophgo/
+X: arch/riscv/boot/dts/spacemit/
RISC-V PMU DRIVERS
M: Atish Patra <atishp@atishpatra.org>
@@ -21004,6 +21005,13 @@ W: https://linuxtv.org
Q: http://patchwork.linuxtv.org/project/linux-media/list/
F: drivers/media/dvb-frontends/sp2*
+SPACEMIT DEVICETREES and DRIVERS
+M: Yangyu Chen <cyy@cyyself.name>
+M: Yixun Lan <dlan@gentoo.org>
+S: Maintained
+F: Documentation/devicetree/bindings/riscv/spacemit.yaml
+F: arch/riscv/boot/dts/spacemit/
+
SPANISH DOCUMENTATION
M: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
R: Avadhut Naik <avadhut.naik@amd.com>
Thanks,
Yangyu Chen
> --
> Yixun Lan (dlan)
> Gentoo Linux Developer
> GPG Key ID AABEFD55
next prev parent reply other threads:[~2024-06-17 2:00 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 17:18 [PATCH v1 0/9] riscv: add initial support for SpacemiT K1 Yangyu Chen
2024-06-16 17:20 ` [PATCH v1 1/9] dt-bindings: vendor-prefixes: add spacemit Yangyu Chen
2024-06-18 15:46 ` Conor Dooley
2024-06-16 17:20 ` [PATCH v1 2/9] dt-bindings: riscv: Add SpacemiT X60 compatibles Yangyu Chen
2024-06-18 15:45 ` Conor Dooley
2024-06-16 17:20 ` [PATCH v1 3/9] dt-bindings: riscv: add SpacemiT K1 bindings Yangyu Chen
2024-06-16 18:42 ` Rob Herring (Arm)
2024-06-18 15:45 ` Conor Dooley
2024-06-16 17:20 ` [PATCH v1 4/9] dt-bindings: timer: Add SpacemiT K1 CLINT Yangyu Chen
2024-06-18 15:40 ` Conor Dooley
2024-06-18 15:48 ` Yangyu Chen
2024-06-18 17:05 ` Conor Dooley
2024-06-16 17:20 ` [PATCH v1 5/9] dt-bindings: interrupt-controller: Add SpacemiT K1 PLIC Yangyu Chen
2024-06-18 15:44 ` Conor Dooley
2024-06-16 17:20 ` [PATCH v1 6/9] riscv: add SpacemiT SOC family Kconfig support Yangyu Chen
2024-06-16 22:26 ` Yixun Lan
2024-06-17 2:12 ` Yangyu Chen
2024-06-16 23:06 ` Yixun Lan
2024-06-17 2:12 ` Yangyu Chen
2024-06-16 17:20 ` [PATCH v1 7/9] riscv: dts: add initial SpacemiT K1 SoC device tree Yangyu Chen
2024-06-16 22:53 ` Yixun Lan
2024-06-17 2:10 ` Yangyu Chen
2024-06-17 6:02 ` Yixun Lan
2024-06-17 7:31 ` Conor Dooley
2024-06-17 12:49 ` Jisheng Zhang
2024-06-17 13:29 ` Conor Dooley
2024-06-17 13:31 ` Jisheng Zhang
2024-06-17 17:01 ` Yangyu Chen
2024-06-16 17:20 ` [PATCH v1 8/9] riscv: dts: spacemit: add Banana Pi BPI-F3 board " Yangyu Chen
2024-06-16 22:31 ` Yixun Lan
2024-06-17 2:16 ` Yangyu Chen
2024-06-16 17:20 ` [PATCH v1 9/9] riscv: defconfig: enable SpacemiT SoC Yangyu Chen
2024-06-16 18:35 ` [PATCH v1 0/9] riscv: add initial support for SpacemiT K1 Conor Dooley
2024-06-16 22:48 ` Yixun Lan
2024-06-17 2:00 ` Yangyu Chen [this message]
2024-06-17 7:28 ` Conor Dooley
2024-06-17 8:15 ` Icenowy Zheng
2024-06-17 14:11 ` Jisheng Zhang
2024-06-17 15:32 ` Conor Dooley
2024-06-17 16:39 ` Yangyu Chen
2024-06-17 17:14 ` Conor Dooley
2024-06-17 17:42 ` Yangyu Chen
2024-06-18 6:58 ` Conor Dooley
2024-06-18 4:39 ` Jisheng Zhang
2024-06-18 4:34 ` Jisheng Zhang
2024-06-18 10:16 ` Conor Dooley
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=tencent_2ABAC5E885F8354EF1F9084A6B5B398EE00A@qq.com \
--to=cyy@cyyself.name \
--cc=anup.patel@wdc.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=jesse@rivosinc.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.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).