From: patchwork-bot+linux-riscv@kernel.org
To: Yixun Lan <dlan@gentoo.org>
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@rivosinc.com,
conor.dooley@microchip.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: Mon, 03 Feb 2025 19:15:36 +0000 [thread overview]
Message-ID: <173861013603.3409359.4773072632762735715.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240730-k1-01-basic-dt-v5-0-98263aae83be@gentoo.org>
Hello:
This series was applied to riscv/linux.git (fixes)
by Yixun Lan <dlan@gentoo.org>:
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
(no matching commit)
- [v5,02/10] dt-bindings: riscv: Add SpacemiT X60 compatibles
https://git.kernel.org/riscv/c/16c9147e6a6c
- [v5,03/10] dt-bindings: riscv: add SpacemiT K1 bindings
https://git.kernel.org/riscv/c/244fe889b950
- [v5,04/10] dt-bindings: timer: Add SpacemiT K1 CLINT
https://git.kernel.org/riscv/c/e5164af2a2fe
- [v5,05/10] dt-bindings: interrupt-controller: Add SpacemiT K1 PLIC
https://git.kernel.org/riscv/c/562272a287d5
- [v5,06/10] dt-bindings: serial: 8250: Add SpacemiT K1 uart compatible
https://git.kernel.org/riscv/c/dfe6d083edff
- [v5,07/10] riscv: add SpacemiT SoC family Kconfig support
https://git.kernel.org/riscv/c/8814aa123adb
- [v5,08/10] riscv: dts: add initial SpacemiT K1 SoC device tree
https://git.kernel.org/riscv/c/d8fe64691955
- [v5,09/10] riscv: dts: spacemit: add Banana Pi BPI-F3 board device tree
https://git.kernel.org/riscv/c/d60d57ab6b2a
- [v5,10/10] riscv: defconfig: enable SpacemiT SoC
https://git.kernel.org/riscv/c/21bef40ad121
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-03 19:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 0:28 [PATCH v5 00/10] riscv: add initial support for SpacemiT K1 Yixun Lan
2024-07-30 0:28 ` [PATCH v5 01/10] dt-bindings: vendor-prefixes: add spacemit Yixun Lan
2024-07-30 0:28 ` [PATCH v5 02/10] dt-bindings: riscv: Add SpacemiT X60 compatibles Yixun Lan
2024-07-30 0:28 ` [PATCH v5 03/10] dt-bindings: riscv: add SpacemiT K1 bindings Yixun Lan
2024-07-30 0:28 ` [PATCH v5 04/10] dt-bindings: timer: Add SpacemiT K1 CLINT Yixun Lan
2024-07-30 0:28 ` [PATCH v5 05/10] dt-bindings: interrupt-controller: Add SpacemiT K1 PLIC Yixun Lan
2024-07-30 0:28 ` [PATCH v5 06/10] dt-bindings: serial: 8250: Add SpacemiT K1 uart compatible Yixun Lan
2024-07-30 0:28 ` [PATCH v5 07/10] riscv: add SpacemiT SoC family Kconfig support Yixun Lan
2024-07-30 0:28 ` [PATCH v5 08/10] riscv: dts: add initial SpacemiT K1 SoC device tree Yixun Lan
2024-08-01 15:57 ` Jesse Taube
2024-07-30 0:28 ` [PATCH v5 09/10] riscv: dts: spacemit: add Banana Pi BPI-F3 board " Yixun Lan
2024-08-01 15:57 ` Jesse Taube
2024-07-30 0:28 ` [PATCH v5 10/10] riscv: defconfig: enable SpacemiT SoC Yixun Lan
2024-09-17 13:04 ` [PATCH v5 00/10] riscv: add initial support for SpacemiT K1 Palmer Dabbelt
2024-09-17 21:08 ` Conor Dooley
2024-10-18 17:24 ` Conor Dooley
2024-10-18 23:46 ` Yixun Lan
2024-12-11 22:33 ` patchwork-bot+linux-riscv
2024-12-12 10:19 ` Yixun Lan
2024-12-15 15:04 ` Conor Dooley
2024-12-19 1:19 ` Yixun Lan
2025-01-04 2:22 ` (subset) " Yixun Lan
2025-02-03 19:15 ` patchwork-bot+linux-riscv [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=173861013603.3409359.4773072632762735715.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cyy@cyyself.name \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=gregkh@linuxfoundation.org \
--cc=inochiama@outlook.com \
--cc=jesse@rivosinc.com \
--cc=jirislaby@kernel.org \
--cc=jszhang@kernel.org \
--cc=kevin.z.m@hotmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=matthias.bgg@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@linutronix.de \
--cc=zhangmeng.kevin@spacemit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).