Re: [PATCH v5 00/10] riscv: add initial support for SpacemiT K1

From: Yixun Lan <dlan@gentoo.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: linux-riscv@lists.infradead.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, cyy@cyyself.name,
	daniel.lezcano@linaro.org, tglx@linutronix.de,
	samuel.holland@sifive.com, anup@brainfault.org,
	gregkh@linuxfoundation.org, jirislaby@kernel.org, lkundrak@v3.sk,
	devicetree@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Jesse Taube <mr.bossman075@gmail.com>,
	inochiama@outlook.com, zhangmeng.kevin@spacemit.com,
	jszhang@kernel.org, matthias.bgg@kernel.org,
	kevin.z.m@hotmail.com
Subject: Re: [PATCH v5 00/10] riscv: add initial support for SpacemiT K1
Date: Thu, 12 Dec 2024 18:19:01 +0800	[thread overview]
Message-ID: <20241212101901-GYA2292414@gentoo> (raw)
In-Reply-To: <173395638199.1729195.1529576042123666894.git-patchwork-notify@kernel.org>

Hi Conor:

On 22:33 Wed 11 Dec     , patchwork-bot+linux-riscv@kernel.org wrote:
> Hello:
> 
> This series was applied to riscv/linux.git (fixes)
> by Conor Dooley <conor.dooley@microchip.com>:
> 
> On Tue, 30 Jul 2024 00:28:03 +0000 you wrote:
> > SpacemiT K1 is an ideal chip for some new extension such as RISC-V Vector
> > 1.0 and Zicond evaluation now. Add initial support for it to allow more
> > people to participate in building drivers to mainline for it.
> > 
> > This kernel has been tested upon Banana Pi BPI-F3 board on vendor U-Boot
> > bootflow generated by Armbian SDK[1] and patched OpenSBI[2] to enable
> > Zicboz, which does not in the vendor dts on its U-Boot. Then successfully
> > booted to busybox on initrd with this log[3].
> > 
> > [...]
> 
> Here is the summary with links:
>   - [v5,01/10] dt-bindings: vendor-prefixes: add spacemit
>     https://git.kernel.org/riscv/c/7cf3e9bfc63d
If I understand correctly, only patch [01/10] of this series was accepted
to 6.13-rc1

for the rest of patches, they would be expected to go through SpacemiT's
SoC tree? which should I take care of them.. so if no objection, I'd like to
queue them at branch k1/dt-for-next [1] first, we might rebase or revert if
something happens before merging (since the clock driver is still under review)

Let me know what you think..

Link: https://github.com/spacemit-com/linux/tree/k1/dt-for-next [1]

>   - [v5,02/10] dt-bindings: riscv: Add SpacemiT X60 compatibles
>     (no matching commit)
>   - [v5,03/10] dt-bindings: riscv: add SpacemiT K1 bindings
>     (no matching commit)
>   - [v5,04/10] dt-bindings: timer: Add SpacemiT K1 CLINT
>     (no matching commit)
>   - [v5,05/10] dt-bindings: interrupt-controller: Add SpacemiT K1 PLIC
>     (no matching commit)
>   - [v5,06/10] dt-bindings: serial: 8250: Add SpacemiT K1 uart compatible
>     (no matching commit)
>   - [v5,07/10] riscv: add SpacemiT SoC family Kconfig support
>     (no matching commit)
>   - [v5,08/10] riscv: dts: add initial SpacemiT K1 SoC device tree
>     (no matching commit)
>   - [v5,09/10] riscv: dts: spacemit: add Banana Pi BPI-F3 board device tree
>     (no matching commit)
>   - [v5,10/10] riscv: defconfig: enable SpacemiT SoC
>     (no matching commit)
> 
> You are awesome, thank you!
> -- 
> Deet-doot-dot, I am a bot.
> https://korg.docs.kernel.org/patchwork/pwbot.html
> 
> 

-- 
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv