On Fri, Mar 21, 2025 at 11:29:27AM +0000, Pinkesh Vaghela wrote: > On Fri, Mar 21, 2025 at 3:07 PM, Krzysztof Kozlowski wrote: > > > On Thu, Mar 20, 2025 at 10:39:52AM +0000, Pinkesh Vaghela wrote: > > >> 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? > > Correct. Once the patches are reviewed, will send separate patches to @soc > and then apply to the git tree. No, that's the wrong order. You apply reviewed patches to the git tree, they then appear in linux-next, after some time soaking there, you send a PR (or in your case patches) to soc@xxxxxxxxxx, usually around rc6 or rc7. Fixes get applied to a different branch and can be sent at any time. I expect both branches to appear in linux-next. Bear in mind that patches for this SoC might be sent by other people, for example me if I find some issues, and you'll need to forward those on to soc@xxxxxxxxxx on top of whatever work you're doing to bring up the SoC. > > > 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.
Attachment:
signature.asc
Description: PGP signature
