linux-kernel - Re: [External] Re: [PATCH v4 0/7] Basic device tree support for ESWIN EIC7700 RISC-V SoC

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: <20250805-equinox-setup-cd37520d2586@spud>
Date: Tue, 5 Aug 2025 15:21:09 +0100
From: Conor Dooley <conor@...nel.org>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Pinkesh Vaghela <pinkesh.vaghela@...fochips.com>,
	Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Paul Walmsley <paul.walmsley@...ive.com>,
	Samuel Holland <samuel.holland@...ive.com>,
	Palmer Dabbelt <palmer@...belt.com>,
	Albert Ou <aou@...s.berkeley.edu>,
	Daniel Lezcano <daniel.lezcano@...aro.org>,
	Min Lin <linmin@...incomputing.com>,
	Pritesh Patel <pritesh.patel@...fochips.com>,
	Yangyu Chen <cyy@...self.name>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
	Yu Chien Peter Lin <peterlin@...estech.com>,
	Charlie Jenkins <charlie@...osinc.com>,
	Kanak Shilledar <kanakshilledar@...il.com>,
	Darshan Prajapati <darshan.prajapati@...fochips.com>,
	Neil Armstrong <neil.armstrong@...aro.org>,
	Heiko Stuebner <heiko@...ech.de>, Aradhya Bhatia <a-bhatia1@...com>,
	"rafal@...ecki.pl" <rafal@...ecki.pl>,
	Anup Patel <anup@...infault.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [External] Re: [PATCH v4 0/7] Basic device tree support for
 ESWIN EIC7700 RISC-V SoC

On Mon, Aug 04, 2025 at 04:45:10PM +0200, Krzysztof Kozlowski wrote:
> On 04/08/2025 15:10, Pinkesh Vaghela wrote:
> > Hello Krzysztof,
> > 
> > Sorry to bother you. I pinged because we addressed all the review comments of V3 in V4. But on V4 we have not received any comments since last 6 weeks.
> > Could you please let us know what should be the further steps?
> 
> Please don't top post.
> 
> That is a bit different question than you asked before: "Gentle reminder
> to review DT patches.".
> 
> Please read SoC subsystem maintainer profile document. For ARM platforms
> you would send now pull request or patches to soc.
> 
> I would suggest following standard SoC way, same as for every other new
> SoC (but carefully observe the kernel process cycle). You can easily
> check archives to see how people also did it...

Yes, standard SoC way please. Arnd expressed recently a preference for
the initial series for a new SoC vendor to go as a patchset to
soc@...ts.linux.dev rather than as a pull-request.

> For RISC-V - not sure
> some trees are handled by Conor, but rest go directly to soc tree.

I'm only doing the canaan/sifive/microchip/starfive ones that were there
when I started, all the "new" platforms have dedicated maintainers that
send direct to Arnd.

Cheers,
Conor.

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)