[PW_SID:978023] Linux SBI MPXY and RPMI drivers by linux-riscv-bot · Pull Request #595 · linux-riscv/linux

linux-riscv-bot · 2025-07-02T08:24:48Z

PR for series 978023 applied to workflow__riscv__fixes

Name: Linux SBI MPXY and RPMI drivers
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=978023
Version: 7

Add device tree bindings for the common RISC-V Platform Management Interface (RPMI) shared memory transport as a mailbox controller. Reviewed-by: Conor Dooley <conor.dooley@microchip.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add device tree bindings for the RISC-V SBI Message Proxy (MPXY) extension as a mailbox controller. Reviewed-by: Conor Dooley <conor.dooley@microchip.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add defines for the new SBI message proxy extension which is part of the SBI v3.0 specification. Reviewed-by: Atish Patra <atishp@rivosinc.com> Co-developed-by: Rahul Pathak <rpathak@ventanamicro.com> Signed-off-by: Rahul Pathak <rpathak@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

The RPMI based mailbox controller drivers and mailbox clients need to share defines related to RPMI messages over mailbox interface so add a common header for this purpose. Co-developed-by: Rahul Pathak <rpathak@ventanamicro.com> Signed-off-by: Rahul Pathak <rpathak@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Introduce optional fw_node() callback which allows a mailbox controller driver to provide controller specific mapping using fwnode. The Linux OF framework already implements fwnode operations for the Linux DD framework so the fw_xlate() callback works fine with device tree as well. Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add common memcpy APIs for copying u32 array to/from __le32 array. Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add a mailbox controller driver for the new SBI message proxy extension which is part of the SBI v3.0 specification. Co-developed-by: Rahul Pathak <rpathak@ventanamicro.com> Signed-off-by: Rahul Pathak <rpathak@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add device tree bindings for the RPMI clock service group based message proxy implemented by the SBI implementation (machine mode firmware or hypervisor). The RPMI clock service group is defined by the RISC-V platform management interface (RPMI) specification. Reviewed-by: Conor Dooley <conor.dooley@microchip.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add device tree bindings for the RPMI clock service group based controller for the supervisor software. The RPMI clock service group is defined by the RISC-V platform management interface (RPMI) specification. Reviewed-by: Conor Dooley <conor.dooley@microchip.com> Reviewed-by: Stephen Boyd <sboyd@kernel.org> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

The RPMI specification defines a clock service group which can be accessed via SBI MPXY extension or dedicated S-mode RPMI transport. Add mailbox client based clock driver for the RISC-V RPMI clock service group. Reviewed-by: Stephen Boyd <sboyd@kernel.org> Co-developed-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Rahul Pathak <rpathak@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add device tree bindings for the RPMI system MSI service group based message proxy implemented by the SBI implementation (machine mode firmware or hypervisor). The RPMI system MSI service group is defined by the RISC-V platform management interface (RPMI) specification. Reviewed-by: Atish Patra <atishp@rivosinc.com> Reviewed-by: Conor Dooley <conor.dooley@microchip.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add device tree bindings for the RPMI system MSI service group based interrupt controller for the supervisor software. The RPMI system MSI service group is defined by the RISC-V platform management interface (RPMI) specification. Reviewed-by: Atish Patra <atishp@rivosinc.com> Reviewed-by: Conor Dooley <conor.dooley@microchip.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

The RPMI specification defines a system MSI service group which allows application processors to receive MSIs upon system events such as graceful shutdown/reboot request, CPU hotplug event, memory hotplug event, etc. Add an irqchip driver for the RISC-V RPMI system MSI service group to directly receive system MSIs in Linux kernel. Reviewed-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Currently acpi_fwnode_get_reference_args() calls the public function __acpi_node_get_property_reference() which ignores the nargs_prop parameter. To fix this, make __acpi_node_get_property_reference() to call the static acpi_fwnode_get_reference() so that callers of fwnode_get_reference_args() can still pass a valid property name to fetch the number of arguments. Signed-off-by: Sunil V L <sunilvl@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Currently, ACPI doesn't support cells property when fwnode_property_get_reference_args() is called. ACPI always expects the number of arguments to be passed. However, the above mentioned call being a common interface for OF and ACPI, it is better to have single calling convention which works for both. Hence, add support for cells property on the reference device to get the number of arguments dynamically. Signed-off-by: Sunil V L <sunilvl@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

The RPMI System MSI interrupt controller (just like PLIC and APLIC) needs to probed prior to devices like GED which use interrupts provided by it. Also, it has dependency on the SBI MPXY mailbox device. Add HIDs of RPMI System MSI and SBI MPXY mailbox devices to the honor list so that those dependencies are handled. Reviewed-by: Atish Patra <atishp@rivosinc.com> Signed-off-by: Sunil V L <sunilvl@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Currently, the interrupt controller list is created without any order. Create the list sorted with the GSI base of the interrupt controllers. Signed-off-by: Sunil V L <sunilvl@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Some RISC-V interrupt controllers like RPMI based system MSI interrupt controllers do not have MADT entry defined. These interrupt controllers exist only in the namespace. ACPI spec defines _GSB method to get the GSI base of the interrupt controller, However, there is no such standard method to get the GSI range. To support such interrupt controllers, set the GSI range of such interrupt controllers to non-overlapping range and provide API for interrupt controller driver to update it with proper value. Signed-off-by: Sunil V L <sunilvl@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

The RPMI System MSI device will provide GSIs to downstream devices (such as GED) so add it to the RISC-V GSI to fwnode mapping. Signed-off-by: Sunil V L <sunilvl@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

ACPI based loadable drivers which need MSIs will also need imsic_acpi_get_fwnode() to update the device MSI domain so export this function. Reviewed-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Sunil V L <sunilvl@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add ACPI support for the RISC-V SBI message proxy (MPXY) based mailbox driver. Signed-off-by: Sunil V L <sunilvl@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add ACPI support for the RISC-V RPMI system MSI based irqchip driver. Reviewed-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Sunil V L <sunilvl@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

The GPIO keyboard and event device can be used to receive graceful shutdown or reboot input keys so let us enable it by default for RV64 (just like ARM64). Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add Rahul and myself as maintainers for RISC-V RPMI and MPXY drivers. Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

linux-riscv-bot · 2025-07-02T08:30:30Z

Patch 1: "[v7,01/24] dt-bindings: mailbox: Add bindings for RPMI shared memory transport"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 103.98 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T08:46:06Z

Patch 1: "[v7,01/24] dt-bindings: mailbox: Add bindings for RPMI shared memory transport"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 934.31 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T09:06:54Z

Patch 1: "[v7,01/24] dt-bindings: mailbox: Add bindings for RPMI shared memory transport"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1247.15 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T09:07:16Z

Patch 1: "[v7,01/24] dt-bindings: mailbox: Add bindings for RPMI shared memory transport"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 20.62 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T09:07:40Z

Patch 1: "[v7,01/24] dt-bindings: mailbox: Add bindings for RPMI shared memory transport"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 21.89 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T15:37:12Z

Patch 9: "[v7,09/24] dt-bindings: clock: Add RPMI clock service controller bindings"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 930.80 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T15:58:24Z

Patch 9: "[v7,09/24] dt-bindings: clock: Add RPMI clock service controller bindings"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1271.06 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T15:58:47Z

Patch 9: "[v7,09/24] dt-bindings: clock: Add RPMI clock service controller bindings"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 20.75 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T15:59:10Z

Patch 9: "[v7,09/24] dt-bindings: clock: Add RPMI clock service controller bindings"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 21.77 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T15:59:13Z

Patch 9: "[v7,09/24] dt-bindings: clock: Add RPMI clock service controller bindings"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 1.66 seconds
Result: WARNING
Output:

WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#23: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 64 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

Commit b5ed16bac12c ("dt-bindings: clock: Add RPMI clock service controller bindings") has style problems, please review.

NOTE: Ignored message types: ALLOC_SIZEOF_STRUCT CAMELCASE COMMIT_LOG_LONG_LINE GIT_COMMIT_ID MACRO_ARG_REUSE NO_AUTHOR_SIGN_OFF

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.
total: 0 errors, 1 warnings, 0 checks, 64 lines checked
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?

linux-riscv-bot · 2025-07-02T16:00:25Z

Patch 9: "[v7,09/24] dt-bindings: clock: Add RPMI clock service controller bindings"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 70.98 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T16:00:27Z

Patch 9: "[v7,09/24] dt-bindings: clock: Add RPMI clock service controller bindings"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.24 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T16:00:30Z

Patch 9: "[v7,09/24] dt-bindings: clock: Add RPMI clock service controller bindings"
kdoc
Desc: Detects for kdoc errors
Duration: 0.87 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T16:00:32Z

Patch 9: "[v7,09/24] dt-bindings: clock: Add RPMI clock service controller bindings"
module-param
Desc: Detect module_param changes
Duration: 0.25 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T16:00:34Z

Patch 9: "[v7,09/24] dt-bindings: clock: Add RPMI clock service controller bindings"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.46 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T16:00:36Z

Patch 9: "[v7,09/24] dt-bindings: clock: Add RPMI clock service controller bindings"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.32 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T16:02:36Z

Patch 10: "[v7,10/24] clk: Add clock driver for the RISC-V RPMI clock service group"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 103.90 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T16:34:03Z

Patch 10: "[v7,10/24] clk: Add clock driver for the RISC-V RPMI clock service group"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 1886.04 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:14:13Z

Patch 10: "[v7,10/24] clk: Add clock driver for the RISC-V RPMI clock service group"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 2407.57 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:14:35Z

Patch 10: "[v7,10/24] clk: Add clock driver for the RISC-V RPMI clock service group"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 20.48 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:14:58Z

Patch 10: "[v7,10/24] clk: Add clock driver for the RISC-V RPMI clock service group"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 22.07 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:15:03Z

Patch 10: "[v7,10/24] clk: Add clock driver for the RISC-V RPMI clock service group"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 3.04 seconds
Result: WARNING
Output:

WARNING: please write a help paragraph that fully describes the config symbol with at least 4 lines
#34: FILE: drivers/clk/Kconfig:496:
+config COMMON_CLK_RPMI
+	tristate "Clock driver based on RISC-V RPMI"
+	depends on MAILBOX
+	default RISCV
+	help
+	  Support for clocks based on the clock service group defined by
+	  the RISC-V platform management interface (RPMI) specification.
+

WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#58: 
new file mode 100644

total: 0 errors, 2 warnings, 0 checks, 673 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

Commit b907b9df1e28 ("clk: Add clock driver for the RISC-V RPMI clock service group") has style problems, please review.

NOTE: Ignored message types: ALLOC_SIZEOF_STRUCT CAMELCASE COMMIT_LOG_LONG_LINE GIT_COMMIT_ID MACRO_ARG_REUSE NO_AUTHOR_SIGN_OFF

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.
total: 0 errors, 2 warnings, 0 checks, 673 lines checked
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
WARNING: please write a help paragraph that fully describes the config symbol with at least 4 lines

linux-riscv-bot · 2025-07-02T17:16:16Z

Patch 10: "[v7,10/24] clk: Add clock driver for the RISC-V RPMI clock service group"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 71.78 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:16:18Z

Patch 10: "[v7,10/24] clk: Add clock driver for the RISC-V RPMI clock service group"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.26 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:16:20Z

Patch 10: "[v7,10/24] clk: Add clock driver for the RISC-V RPMI clock service group"
kdoc
Desc: Detects for kdoc errors
Duration: 0.90 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:16:22Z

Patch 10: "[v7,10/24] clk: Add clock driver for the RISC-V RPMI clock service group"
module-param
Desc: Detect module_param changes
Duration: 0.27 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:16:23Z

Patch 10: "[v7,10/24] clk: Add clock driver for the RISC-V RPMI clock service group"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.40 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:16:25Z

Patch 10: "[v7,10/24] clk: Add clock driver for the RISC-V RPMI clock service group"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.33 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:18:24Z

Patch 11: "[v7,11/24] dt-bindings: Add RPMI system MSI message proxy bindings"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 103.97 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:33:59Z

Patch 11: "[v7,11/24] dt-bindings: Add RPMI system MSI message proxy bindings"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 933.26 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:54:42Z

Patch 11: "[v7,11/24] dt-bindings: Add RPMI system MSI message proxy bindings"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1241.92 seconds
Result: PASS

linux-riscv-bot · 2025-07-02T17:55:05Z

Patch 11: "[v7,11/24] dt-bindings: Add RPMI system MSI message proxy bindings"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 21.45 seconds
Result: PASS

Linux RISC-V bot and others added 25 commits June 27, 2025 17:47

Adding CI files

a7cb30d

mailbox/riscv-sbi-mpxy: Add ACPI support

487ab49

Add ACPI support for the RISC-V SBI message proxy (MPXY) based mailbox driver. Signed-off-by: Sunil V L <sunilvl@ventanamicro.com> Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

MAINTAINERS: Add entry for RISC-V RPMI and MPXY drivers

2f1b1f5

Add Rahul and myself as maintainers for RISC-V RPMI and MPXY drivers. Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

linux-riscv-bot force-pushed the workflow__riscv__fixes branch from a7cb30d to d776861 Compare July 2, 2025 18:46

linux-riscv-bot closed this Jul 4, 2025

linux-riscv-bot deleted the pw978023 branch July 4, 2025 09:21

Conversation

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

linux-riscv-bot commented Jul 2, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants