[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f0dd950a-02a7-402b-a08e-015db458b273@kernel.org>
Date: Fri, 21 Mar 2025 10:37:18 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Conor Dooley <conor@...nel.org>,
Pinkesh Vaghela <pinkesh.vaghela@...fochips.com>
Cc: 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: [PATCH 00/10] Basic device tree support for ESWIN EIC7700 RISC-V
SoC
On 20/03/2025 13:00, Conor Dooley wrote:
> On Thu, Mar 20, 2025 at 10:39:52AM +0000, Pinkesh Vaghela wrote:
>> Hi Conor,
>>
>> On Tue, Mar 11, 2025 at 11:38 PM, Conor Dooley wrote:
>>> On Tue, Mar 11, 2025 at 01:04:22PM +0530, Pinkesh Vaghela wrote:
>>>> Add support for ESWIN EIC7700 SoC consisting of SiFive Quad-Core
>>>> P550 CPU cluster and the first development board that uses it, the
>>>> SiFive HiFive Premier P550.
>>>>
>>>> This patch series adds initial device tree and also adds ESWIN
>>>> architecture support.
>>>>
>>>> Boot-tested using intiramfs with Linux 6.14.0-rc2 on HiFive Premier
>>>> P550 board using U-Boot 2024.01 and OpenSBI 1.4.
>>>
>>> There's no git tree in your MAINTAINERS entry, nor mention here of what the
>>> story is going to be in terms of sending patches to Arnd. Who is going to be
>>> doing that?
>>
>> We are not currently set up for sending signed pull requests,
>> so for now we plan to send changes to Arnd as separate patches.
>
> Undesirable, but sure. You didn't answer the first part of my question
Just to clarify - separate patches as separate postings to soc@ after
the review was done on the lists and then you applied them to the tree
Conor asked below, right?
> though, and there's no git tree listed in your v2 series. That part is
> not negotiable, you have to have one and get it included in linux-next.
Best regards,
Krzysztof
Powered by blists - more mailing lists