From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: dlan@gentoo.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, Paul Walmsley <paul.walmsley@sifive.com>,
cyy@cyyself.name, samuel.holland@sifive.com, anup@brainfault.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, inochiama@outlook.com,
uwu@icenowy.me, zhangmeng.kevin@spacemit.com,
kevin.z.m@hotmail.com, matthias.bgg@kernel.org,
Haylen Chu <heylenay@4d2.org>,
Troy Mitchell <troymitchell988@gmail.com>,
Charlie Jenkins <charlie@rivosinc.com>,
Jesse T <mr.bossman075@gmail.com>
Subject: Re: [PATCH v5 00/10] riscv: add initial support for SpacemiT K1
Date: Fri, 18 Oct 2024 18:24:21 +0100 [thread overview]
Message-ID: <20241018-drapery-stable-cc31a97cda90@spud> (raw)
In-Reply-To: <20240917-spoilage-nimble-a8303fd04482@squawk>
[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]
On Tue, Sep 17, 2024 at 10:08:03PM +0100, Conor Dooley wrote:
> In other news, nobody has really made an "official" statement about who
> is going to maintain this particular platform. People have expressed
> interest (including the submitter of the series, IIRC) but there's no
> MAINTAINERS entry added here AFAICT. I used to have an entry that
> covered arch/riscv/boot/dts/*, with exclusions for sunxi and renesas,
> but with Drew taking on thead and sophgo being the resぽonsibility of
> Chen Wang and Inochi, I no longer have that wildcard.
>
> I'm happy to apply patches for the platform if noone else is interested
> in that side of things, provided there are willing reviewers, but I
> would much rather that someone else took up the responsibility of
> applying patches and sending PRs - and of course I am happy to help
> whoever that is with the process.
On second thoughts (and on a second opinion) I am not actually willing
to apply patches for this platform, since it isn't sustainable to take
on each and every platform that there's no maintainer for.
+CC a few more people that have been involved in the platform.
Yixun Lan, you're kinda the "prime" person to maintain the platform
since you're the one who took up the core support work etc. Is
maintaining the platform, maybe with the help of one of the other folks
working on it something you can do?
Mostly the responsibilities are just applying patches for fixes/new
content and sending PRs to the soc maintainers - but knowing what's
right or not obviously requires familiarity with the platform which
people that work on it are best placed to do. Myself and the soc
maintainers will help if whoever does this runs into any trouble.
There is some documentation here https://docs.kernel.org/process/maintainer-soc.html
that will assist somewhat with getting up to speed with the process
also.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-10-18 17:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 0:28 [PATCH v5 00/10] riscv: add initial support for SpacemiT K1 Yixun Lan
2024-07-30 0:28 ` [PATCH v5 01/10] dt-bindings: vendor-prefixes: add spacemit Yixun Lan
2024-07-30 0:28 ` [PATCH v5 02/10] dt-bindings: riscv: Add SpacemiT X60 compatibles Yixun Lan
2024-07-30 0:28 ` [PATCH v5 03/10] dt-bindings: riscv: add SpacemiT K1 bindings Yixun Lan
2024-07-30 0:28 ` [PATCH v5 04/10] dt-bindings: timer: Add SpacemiT K1 CLINT Yixun Lan
2024-07-30 0:28 ` [PATCH v5 05/10] dt-bindings: interrupt-controller: Add SpacemiT K1 PLIC Yixun Lan
2024-07-30 0:28 ` [PATCH v5 06/10] dt-bindings: serial: 8250: Add SpacemiT K1 uart compatible Yixun Lan
2024-07-30 0:28 ` [PATCH v5 07/10] riscv: add SpacemiT SoC family Kconfig support Yixun Lan
2024-07-30 0:28 ` [PATCH v5 08/10] riscv: dts: add initial SpacemiT K1 SoC device tree Yixun Lan
2024-08-01 15:57 ` Jesse Taube
2024-07-30 0:28 ` [PATCH v5 09/10] riscv: dts: spacemit: add Banana Pi BPI-F3 board " Yixun Lan
2024-08-01 15:57 ` Jesse Taube
2024-07-30 0:28 ` [PATCH v5 10/10] riscv: defconfig: enable SpacemiT SoC Yixun Lan
2024-09-17 13:04 ` [PATCH v5 00/10] riscv: add initial support for SpacemiT K1 Palmer Dabbelt
2024-09-17 21:08 ` Conor Dooley
2024-10-18 17:24 ` Conor Dooley [this message]
2024-10-18 23:46 ` Yixun Lan
2024-12-11 22:33 ` patchwork-bot+linux-riscv
2024-12-12 10:19 ` Yixun Lan
2024-12-15 15:04 ` Conor Dooley
2024-12-19 1:19 ` Yixun Lan
2025-01-04 2:22 ` (subset) " Yixun Lan
2025-02-03 19:15 ` patchwork-bot+linux-riscv
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=20241018-drapery-stable-cc31a97cda90@spud \
--to=conor@kernel.org \
--cc=anup@brainfault.org \
--cc=charlie@rivosinc.com \
--cc=conor+dt@kernel.org \
--cc=cyy@cyyself.name \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=heylenay@4d2.org \
--cc=inochiama@outlook.com \
--cc=kevin.z.m@hotmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=matthias.bgg@kernel.org \
--cc=mr.bossman075@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=troymitchell988@gmail.com \
--cc=uwu@icenowy.me \
--cc=zhangmeng.kevin@spacemit.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).