lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241018234615-GYA2124001@gentoo>
Date: Sat, 19 Oct 2024 07:46:15 +0800
From: Yixun Lan <dlan@...too.org>
To: Conor Dooley <conor@...nel.org>
Cc: Palmer Dabbelt <palmer@...belt.com>, robh@...nel.org,
	krzk+dt@...nel.org, conor+dt@...nel.org,
	Paul Walmsley <paul.walmsley@...ive.com>, cyy@...self.name,
	samuel.holland@...ive.com, anup@...infault.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-riscv@...ts.infradead.org, inochiama@...look.com,
	uwu@...nowy.me, zhangmeng.kevin@...cemit.com, kevin.z.m@...mail.com,
	matthias.bgg@...nel.org, Haylen Chu <heylenay@....org>,
	Troy Mitchell <troymitchell988@...il.com>,
	Charlie Jenkins <charlie@...osinc.com>,
	Jesse T <mr.bossman075@...il.com>
Subject: Re: [PATCH v5 00/10] riscv: add initial support for SpacemiT K1

Hi Conor:

On 18:24 Fri 18 Oct     , Conor Dooley wrote:
> 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.
> 
Ok, I fully understand your concern..

> +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?
> 
That would be sweet, yes, I can take the maintainer responsibitly for now
but, I'm open if someone else willing to help and co-maintain..

> 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.
> 
Great, thanks for the info
> Cheers,
> Conor.

last, one question I'd raise:

for this particular patch series, do you want me to send another version v6
which can update the MAINTAINERS file (nothing changed with the code)

-- 
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ