From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Pinkesh Vaghela <pinkesh.vaghela@einfochips.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Paul Walmsley <paul.walmsley@sifive.com>,
Samuel Holland <samuel.holland@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Min Lin <linmin@eswincomputing.com>,
Pritesh Patel <pritesh.patel@einfochips.com>,
Yangyu Chen <cyy@cyyself.name>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Yu Chien Peter Lin <peterlin@andestech.com>,
Charlie Jenkins <charlie@rivosinc.com>,
Kanak Shilledar <kanakshilledar@gmail.com>,
Darshan Prajapati <darshan.prajapati@einfochips.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Heiko Stuebner <heiko@sntech.de>,
Aradhya Bhatia <a-bhatia1@ti.com>,
"rafal@milecki.pl" <rafal@milecki.pl>,
Anup Patel <anup@brainfault.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [External] Re: [PATCH v4 0/7] Basic device tree support for ESWIN EIC7700 RISC-V SoC
Date: Tue, 5 Aug 2025 15:21:09 +0100 [thread overview]
Message-ID: <20250805-equinox-setup-cd37520d2586@spud> (raw)
In-Reply-To: <72354ec9-7dc8-4192-9c25-d37abf33b5f0@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
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@lists.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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-08-05 14:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 11:23 [PATCH v4 0/7] Basic device tree support for ESWIN EIC7700 RISC-V SoC Pinkesh Vaghela
2025-06-16 11:23 ` [PATCH v4 1/7] dt-bindings: riscv: Add SiFive P550 CPU compatible Pinkesh Vaghela
2025-06-16 11:23 ` [PATCH v4 2/7] riscv: Add Kconfig option for ESWIN platforms Pinkesh Vaghela
2025-06-16 11:23 ` [PATCH v4 3/7] dt-bindings: vendor-prefixes: add eswin Pinkesh Vaghela
2025-08-21 19:11 ` Rob Herring
2025-06-16 11:23 ` [PATCH v4 4/7] dt-bindings: riscv: Add SiFive HiFive Premier P550 board Pinkesh Vaghela
2025-06-16 11:23 ` [PATCH v4 5/7] dt-bindings: interrupt-controller: Add ESWIN EIC7700 PLIC Pinkesh Vaghela
2025-06-16 11:23 ` [PATCH v4 6/7] riscv: dts: add initial support for EIC7700 SoC Pinkesh Vaghela
2025-06-16 11:23 ` [PATCH v4 7/7] riscv: dts: eswin: add HiFive Premier P550 board device tree Pinkesh Vaghela
2025-08-01 10:34 ` [PATCH v4 0/7] Basic device tree support for ESWIN EIC7700 RISC-V SoC Pinkesh Vaghela
2025-08-02 8:34 ` Krzysztof Kozlowski
2025-08-04 13:10 ` [External] " Pinkesh Vaghela
2025-08-04 14:45 ` Krzysztof Kozlowski
2025-08-05 14:21 ` Conor Dooley [this message]
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=20250805-equinox-setup-cd37520d2586@spud \
--to=conor@kernel.org \
--cc=a-bhatia1@ti.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=cyy@cyyself.name \
--cc=daniel.lezcano@linaro.org \
--cc=darshan.prajapati@einfochips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kanakshilledar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linmin@eswincomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterlin@andestech.com \
--cc=pinkesh.vaghela@einfochips.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=pritesh.patel@einfochips.com \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@linutronix.de \
/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