On Thu, Dec 12, 2024 at 06:19:01PM +0800, Yixun Lan wrote: > Hi Conor: > > On 22:33 Wed 11 Dec , patchwork-bot+linux-riscv@xxxxxxxxxx wrote: > > Hello: > > > > This series was applied to riscv/linux.git (fixes) > > by Conor Dooley <conor.dooley@xxxxxxxxxxxxx>: > > > > 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.. Sure. I had grabbed the first patch because a couple trees needed the vendor prefix for peripheral drivers. How is the clock driver getting on? Do you think it is close to being merged?
Attachment:
signature.asc
Description: PGP signature
