[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <72354ec9-7dc8-4192-9c25-d37abf33b5f0@kernel.org>
Date: Mon, 4 Aug 2025 16:45:10 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Pinkesh Vaghela <pinkesh.vaghela@...fochips.com>,
Conor Dooley <conor@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>
Cc: 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 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. For RISC-V - not sure
some trees are handled by Conor, but rest go directly to soc tree.
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...
Best regards,
Krzysztof
Powered by blists - more mailing lists