[GIT PULL] RISC-V Sophgo Devicetrees for v6.17 (v2)

Arnd Bergmann arnd at arndb.de
Tue Jul 22 22:22:47 PDT 2025


On Wed, Jul 23, 2025, at 04:25, Chen Wang wrote:
> On 2025/7/23 4:17, Arnd Bergmann wrote:
>> On Wed, Jul 16, 2025, at 02:31, Chen Wang wrote:

> According to your request, I have rebuilt two branches for PR (temporary):
> https://github.com/sophgo/linux/tree/temp-riscv-sophgo-dt-for-next
> https://github.com/sophgo/linux/tree/temp-arm-sophgo-dt-for-next
>
> Please check whether it meets your requirements. Both branches are based 
> on v6.16-rc1. If there is no problem, I will submit PRs using these two 
> branches respectively.

Thanks a lot for updating the contents so quickly, this all looks
good to me.

> It should be noted that about the commit "610f943a66be dt-bindings: soc: 
> sophgo: Move SoCs/boards from riscv into soc, add SG2000" on 
> temp-riscv-sophgo-dt-for-next. This change was originally made for 
> SG2000/ARM, moving sophgo.yaml from the riscv directory to soc/sophgo 
> for sharing between riscv and arm. Because this file will also be 
> involved in subsequent changes for riscv, I placed it in 
> temp-riscv-sophgo-dt-for-next.

Yes, that is fine. Technically what you could do here is to put this
commit on 6.16-rc1 first and then base both of the branches on
the same commit ID. We sometimes do this when there are hard
dependencies on a commit that otherwise prevent bisection. I don't
think it's necessary here.

     Arnd



More information about the linux-riscv mailing list