[PW_SID:973967] RISC-V: turn sbi_ecall into a variadic macro by linux-riscv-bot · Pull Request #554 · linux-riscv/linux

linux-riscv-bot · 2025-06-19T19:17:21Z

PR for series 973967 applied to workflow__riscv__fixes

Name: RISC-V: turn sbi_ecall into a variadic macro
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=973967
Version: 2

The SBI ecall interface has 0~6 arguments in a0~a5, and undefined arguments are not reserved, so we don't have to zero the registers. The current sbi_ecall forces programmers to pad the argument count, which makes it hard to distinguish what is a value 0, and what is the padding, because 0 was traditionally used for padding as well. Turn sbi_ecall into a variadic macro that accepts 2~8 arguments, and where only the specified arguments get passed to the ecall instruction. The register a1 is zeroed if unused, to prevent unnecessary leaks of kernel register state from the tracepoints. Signed-off-by: Radim Krčmář <rkrcmar@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

The new sbi_ecall doesn't have to list all 8 arguments anymore, so only pass the actual numbers of arguments for each SBI function. The remaining trailing 0 are intentional as they represent an argument. SBI 0.1 shouldn't be using the sbi_ecall, because it's only for 0.2+, but allow it by passing 0 is the reserved register. Signed-off-by: Radim Krčmář <rkrcmar@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Tracepoits generate bad code in the non-trace path. The acceptable tracepoint overhead in the non-tracing path is a nop, and possibly a second 2 byte nop for alignment, but the actual overhead is way higher. For example, the sbi_fwft_set with tracepoints: 0xffffffff80022ee8 <+0>: auipc a5,0x2cec 0xffffffff80022eec <+4>: lbu a5,1704(a5) # 0xffffffff82d0f590 <sbi_fwft_supported> 0xffffffff80022ef0 <+8>: beqz a5,0xffffffff80022fa0 <sbi_fwft_set+184> 0xffffffff80022ef2 <+10>: addi sp,sp,-48 0xffffffff80022ef4 <+12>: sd s0,32(sp) 0xffffffff80022ef6 <+14>: sd s1,24(sp) 0xffffffff80022ef8 <+16>: sd s2,16(sp) 0xffffffff80022efa <+18>: sd ra,40(sp) 0xffffffff80022efc <+20>: addi s0,sp,48 0xffffffff80022efe <+22>: slli s1,a0,0x20 0xffffffff80022f02 <+26>: mv s2,a1 0xffffffff80022f04 <+28>: srli s1,s1,0x20 0xffffffff80022f06 <+30>: nop 0xffffffff80022f08 <+32>: nop 0xffffffff80022f0c <+36>: lui a7,0x46574 0xffffffff80022f10 <+40>: mv a0,s1 0xffffffff80022f12 <+42>: mv a1,s2 0xffffffff80022f14 <+44>: addi a7,a7,1620 # 0x46574654 0xffffffff80022f18 <+48>: li a6,0 0xffffffff80022f1a <+50>: ecall 0xffffffff80022f1e <+54>: mv s1,a0 0xffffffff80022f20 <+56>: nop 0xffffffff80022f24 <+60>: addiw a0,s1,14 0xffffffff80022f28 <+64>: li a5,14 0xffffffff80022f2a <+66>: bltu a5,a0,0xffffffff80022f9a <sbi_fwft_set+178> 0xffffffff80022f2e <+70>: slli a5,a0,0x20 0xffffffff80022f32 <+74>: srli a0,a5,0x1e 0xffffffff80022f36 <+78>: auipc a5,0x1c75 0xffffffff80022f3a <+82>: addi a5,a5,-886 # 0xffffffff81c97bc0 <CSWTCH.177> 0xffffffff80022f3e <+86>: add a5,a5,a0 0xffffffff80022f40 <+88>: lw a0,0(a5) 0xffffffff80022f42 <+90>: ld ra,40(sp) 0xffffffff80022f44 <+92>: ld s0,32(sp) 0xffffffff80022f46 <+94>: ld s1,24(sp) 0xffffffff80022f48 <+96>: ld s2,16(sp) 0xffffffff80022f4a <+98>: addi sp,sp,48 0xffffffff80022f4c <+100>: ret [tracepoint slowpaths] 0xffffffff80022f9a <+178>: li a0,-524 0xffffffff80022f9e <+182>: j 0xffffffff80022f42 <sbi_fwft_set+90> 0xffffffff80022fa0 <+184>: li a0,-95 0xffffffff80022fa4 <+188>: ret Without tracepoints: 0xffffffff80022b40 <+0>: addi sp,sp,-16 0xffffffff80022b42 <+2>: sd s0,0(sp) 0xffffffff80022b44 <+4>: sd ra,8(sp) 0xffffffff80022b46 <+6>: addi s0,sp,16 0xffffffff80022b48 <+8>: auipc a5,0x2ced 0xffffffff80022b4c <+12>: lbu a5,-1464(a5) # 0xffffffff82d0f590 <sbi_fwft_supported> 0xffffffff80022b50 <+16>: beqz a5,0xffffffff80022b8e <sbi_fwft_set+78> 0xffffffff80022b52 <+18>: lui a7,0x46574 0xffffffff80022b56 <+22>: slli a0,a0,0x20 0xffffffff80022b58 <+24>: srli a0,a0,0x20 0xffffffff80022b5a <+26>: addi a7,a7,1620 # 0x46574654 0xffffffff80022b5e <+30>: li a6,0 0xffffffff80022b60 <+32>: ecall 0xffffffff80022b64 <+36>: li a5,14 0xffffffff80022b66 <+38>: addiw a0,a0,14 0xffffffff80022b68 <+40>: bltu a5,a0,0xffffffff80022b88 <sbi_fwft_set+72> 0xffffffff80022b6c <+44>: slli a5,a0,0x20 0xffffffff80022b70 <+48>: srli a0,a5,0x1e 0xffffffff80022b74 <+52>: auipc a5,0x1c75 0xffffffff80022b78 <+56>: addi a5,a5,-300 # 0xffffffff81c97a48 <CSWTCH.176> 0xffffffff80022b7c <+60>: add a5,a5,a0 0xffffffff80022b7e <+62>: lw a0,0(a5) 0xffffffff80022b80 <+64>: ld ra,8(sp) 0xffffffff80022b82 <+66>: ld s0,0(sp) 0xffffffff80022b84 <+68>: addi sp,sp,16 0xffffffff80022b86 <+70>: ret 0xffffffff80022b88 <+72>: li a0,-524 0xffffffff80022b8c <+76>: j 0xffffffff80022b80 <sbi_fwft_set+64> 0xffffffff80022b8e <+78>: li a0,-95 0xffffffff80022b92 <+82>: j 0xffffffff80022b80 <sbi_fwft_set+64> It would be nice if RISC-V had a way to tell compilers to generate the desired code, because if this issue isn't limited to ecall tracepoints, then disabling CONFIG_TRACEPOINTS is starting to look good. :) Signed-off-by: Radim Krčmář <rkrcmar@ventanamicro.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

linux-riscv-bot · 2025-06-19T19:22:33Z

Patch 1: "[v2,1/2] RISC-V: sbi: turn sbi_ecall into variadic macro"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 102.14 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T19:39:41Z

Patch 1: "[v2,1/2] RISC-V: sbi: turn sbi_ecall into variadic macro"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 1027.30 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:04:58Z

Patch 1: "[v2,1/2] RISC-V: sbi: turn sbi_ecall into variadic macro"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1515.48 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:05:21Z

Patch 1: "[v2,1/2] RISC-V: sbi: turn sbi_ecall into variadic macro"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 20.84 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:05:44Z

Patch 1: "[v2,1/2] RISC-V: sbi: turn sbi_ecall into variadic macro"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 22.09 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:05:47Z

Patch 1: "[v2,1/2] RISC-V: sbi: turn sbi_ecall into variadic macro"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 1.94 seconds
Result: ERROR
Output:

CHECK: extern prototypes should be avoided in .h files
#52: FILE: arch/riscv/include/asm/sbi.h:467:
+extern void do_trace_sbi_call(int ext, int fid);

CHECK: extern prototypes should be avoided in .h files
#53: FILE: arch/riscv/include/asm/sbi.h:468:
+extern void do_trace_sbi_return(int ext, long error, long value);

ERROR: Macros with complex values should be enclosed in parentheses
#95: FILE: arch/riscv/include/asm/sbi.h:504:
+#define __sbi_ecall_constraints2  __sbi_ecall_constraints1, "r" (__a6)

BUT SEE:

   do {} while (0) advice is over-stated in a few situations:

   The more obvious case is macros, like MODULE_PARM_DESC, invoked at
   file-scope, where C disallows code (it must be in functions).  See
   $exceptions if you have one to add by name.

   More troublesome is declarative macros used at top of new scope,
   like DECLARE_PER_CPU.  These might just compile with a do-while-0
   wrapper, but would be incorrect.  Most of these are handled by
   detecting struct,union,etc declaration primitives in $exceptions.

   Theres also macros called inside an if (block), which "return" an
   expression.  These cannot do-while, and need a ({}) wrapper.

   Enjoy this qualification while we work to improve our heuristics.

ERROR: Macros with complex values should be enclosed in parentheses
#96: FILE: arch/riscv/include/asm/sbi.h:505:
+#define __sbi_ecall_constraints3  __sbi_ecall_constraints2, "r" (__a0)

BUT SEE:

   do {} while (0) advice is over-stated in a few situations:

   The more obvious case is macros, like MODULE_PARM_DESC, invoked at
   file-scope, where C disallows code (it must be in functions).  See
   $exceptions if you have one to add by name.

   More troublesome is declarative macros used at top of new scope,
   like DECLARE_PER_CPU.  These might just compile with a do-while-0
   wrapper, but would be incorrect.  Most of these are handled by
   detecting struct,union,etc declaration primitives in $exceptions.

   Theres also macros called inside an if (block), which "return" an
   expression.  These cannot do-while, and need a ({}) wrapper.

   Enjoy this qualification while we work to improve our heuristics.

ERROR: Macros with complex values should be enclosed in parentheses
#97: FILE: arch/riscv/include/asm/sbi.h:506:
+#define __sbi_ecall_constraints4  __sbi_ecall_constraints3, "r" (__a1)

BUT SEE:

   do {} while (0) advice is over-stated in a few situations:

   The more obvious case is macros, like MODULE_PARM_DESC, invoked at
   file-scope, where C disallows code (it must be in functions).  See
   $exceptions if you have one to add by name.

   More troublesome is declarative macros used at top of new scope,
   like DECLARE_PER_CPU.  These might just compile with a do-while-0
   wrapper, but would be incorrect.  Most of these are handled by
   detecting struct,union,etc declaration primitives in $exceptions.

   Theres also macros called inside an if (block), which "return" an
   expression.  These cannot do-while, and need a ({}) wrapper.

   Enjoy this qualification while we work to improve our heuristics.

ERROR: Macros with complex values should be enclosed in parentheses
#98: FILE: arch/riscv/include/asm/sbi.h:507:
+#define __sbi_ecall_constraints5  __sbi_ecall_constraints4, "r" (__a2)

BUT SEE:

   do {} while (0) advice is over-stated in a few situations:

   The more obvious case is macros, like MODULE_PARM_DESC, invoked at
   file-scope, where C disallows code (it must be in functions).  See
   $exceptions if you have one to add by name.

   More troublesome is declarative macros used at top of new scope,
   like DECLARE_PER_CPU.  These might just compile with a do-while-0
   wrapper, but would be incorrect.  Most of these are handled by
   detecting struct,union,etc declaration primitives in $exceptions.

   Theres also macros called inside an if (block), which "return" an
   expression.  These cannot do-while, and need a ({}) wrapper.

   Enjoy this qualification while we work to improve our heuristics.

ERROR: Macros with complex values should be enclosed in parentheses
#99: FILE: arch/riscv/include/asm/sbi.h:508:
+#define __sbi_ecall_constraints6  __sbi_ecall_constraints5, "r" (__a3)

BUT SEE:

   do {} while (0) advice is over-stated in a few situations:

   The more obvious case is macros, like MODULE_PARM_DESC, invoked at
   file-scope, where C disallows code (it must be in functions).  See
   $exceptions if you have one to add by name.

   More troublesome is declarative macros used at top of new scope,
   like DECLARE_PER_CPU.  These might just compile with a do-while-0
   wrapper, but would be incorrect.  Most of these are handled by
   detecting struct,union,etc declaration primitives in $exceptions.

   Theres also macros called inside an if (block), which "return" an
   expression.  These cannot do-while, and need a ({}) wrapper.

   Enjoy this qualification while we work to improve our heuristics.

ERROR: Macros with complex values should be enclosed in parentheses
#100: FILE: arch/riscv/include/asm/sbi.h:509:
+#define __sbi_ecall_constraints7  __sbi_ecall_constraints6, "r" (__a4)

BUT SEE:

   do {} while (0) advice is over-stated in a few situations:

   The more obvious case is macros, like MODULE_PARM_DESC, invoked at
   file-scope, where C disallows code (it must be in functions).  See
   $exceptions if you have one to add by name.

   More troublesome is declarative macros used at top of new scope,
   like DECLARE_PER_CPU.  These might just compile with a do-while-0
   wrapper, but would be incorrect.  Most of these are handled by
   detecting struct,union,etc declaration primitives in $exceptions.

   Theres also macros called inside an if (block), which "return" an
   expression.  These cannot do-while, and need a ({}) wrapper.

   Enjoy this qualification while we work to improve our heuristics.

ERROR: Macros with complex values should be enclosed in parentheses
#101: FILE: arch/riscv/include/asm/sbi.h:510:
+#define __sbi_ecall_constraints8  __sbi_ecall_constraints7, "r" (__a5)

BUT SEE:

   do {} while (0) advice is over-stated in a few situations:

   The more obvious case is macros, like MODULE_PARM_DESC, invoked at
   file-scope, where C disallows code (it must be in functions).  See
   $exceptions if you have one to add by name.

   More troublesome is declarative macros used at top of new scope,
   like DECLARE_PER_CPU.  These might just compile with a do-while-0
   wrapper, but would be incorrect.  Most of these are handled by
   detecting struct,union,etc declaration primitives in $exceptions.

   Theres also macros called inside an if (block), which "return" an
   expression.  These cannot do-while, and need a ({}) wrapper.

   Enjoy this qualification while we work to improve our heuristics.

ERROR: Macros starting with if should be enclosed by a do - while loop to avoid possible if/else logic defects
#103: FILE: arch/riscv/include/asm/sbi.h:512:
+#define __sbi_ecall_trace_call() \
+	if (tracepoint_enabled(sbi_call)) \
+		do_trace_sbi_call(__ta7, __ta6)

ERROR: Macros starting with if should be enclosed by a do - while loop to avoid possible if/else logic defects
#107: FILE: arch/riscv/include/asm/sbi.h:516:
+#define __sbi_ecall_trace_return() \
+	if (tracepoint_enabled(sbi_return)) \
+		do_trace_sbi_return(__ta7, __ret.error, __ret.value)

total: 9 errors, 0 warnings, 2 checks, 141 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 502fec74ad13 ("RISC-V: sbi: turn sbi_ecall into variadic macro") 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.
CHECK: extern prototypes should be avoided in .h files
ERROR: Macros starting with if should be enclosed by a do - while loop to avoid possible if/else logic defects
ERROR: Macros with complex values should be enclosed in parentheses

linux-riscv-bot · 2025-06-19T20:07:00Z

Patch 1: "[v2,1/2] RISC-V: sbi: turn sbi_ecall into variadic macro"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 71.45 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:07:02Z

Patch 1: "[v2,1/2] RISC-V: sbi: turn sbi_ecall into variadic macro"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.23 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:07:04Z

Patch 1: "[v2,1/2] RISC-V: sbi: turn sbi_ecall into variadic macro"
kdoc
Desc: Detects for kdoc errors
Duration: 0.89 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:07:07Z

Patch 1: "[v2,1/2] RISC-V: sbi: turn sbi_ecall into variadic macro"
module-param
Desc: Detect module_param changes
Duration: 0.25 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:07:09Z

Patch 1: "[v2,1/2] RISC-V: sbi: turn sbi_ecall into variadic macro"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.22 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:07:11Z

Patch 1: "[v2,1/2] RISC-V: sbi: turn sbi_ecall into variadic macro"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.30 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:09:12Z

Patch 2: "[v2,2/2] RISC-V: make use of variadic sbi_ecall"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 105.21 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:26:18Z

Patch 2: "[v2,2/2] RISC-V: make use of variadic sbi_ecall"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 1024.41 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:51:21Z

Patch 2: "[v2,2/2] RISC-V: make use of variadic sbi_ecall"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1502.28 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:51:44Z

Patch 2: "[v2,2/2] RISC-V: make use of variadic sbi_ecall"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 20.83 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:52:07Z

Patch 2: "[v2,2/2] RISC-V: make use of variadic sbi_ecall"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 22.08 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:52:11Z

Patch 2: "[v2,2/2] RISC-V: make use of variadic sbi_ecall"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 2.36 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:53:23Z

Patch 2: "[v2,2/2] RISC-V: make use of variadic sbi_ecall"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 71.13 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:53:25Z

Patch 2: "[v2,2/2] RISC-V: make use of variadic sbi_ecall"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.23 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:53:27Z

Patch 2: "[v2,2/2] RISC-V: make use of variadic sbi_ecall"
kdoc
Desc: Detects for kdoc errors
Duration: 0.91 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:53:29Z

Patch 2: "[v2,2/2] RISC-V: make use of variadic sbi_ecall"
module-param
Desc: Detect module_param changes
Duration: 0.26 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:53:31Z

Patch 2: "[v2,2/2] RISC-V: make use of variadic sbi_ecall"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.22 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:53:32Z

Patch 2: "[v2,2/2] RISC-V: make use of variadic sbi_ecall"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.30 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T20:55:29Z

Patch 3: "[v2,3/2] RISC-V: sbi: remove sbi_ecall tracepoints"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 101.82 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T21:12:37Z

Patch 3: "[v2,3/2] RISC-V: sbi: remove sbi_ecall tracepoints"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 1027.57 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T21:37:45Z

Patch 3: "[v2,3/2] RISC-V: sbi: remove sbi_ecall tracepoints"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1506.60 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T21:38:08Z

Patch 3: "[v2,3/2] RISC-V: sbi: remove sbi_ecall tracepoints"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 20.79 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T21:38:31Z

Patch 3: "[v2,3/2] RISC-V: sbi: remove sbi_ecall tracepoints"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 21.75 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T21:38:33Z

Patch 3: "[v2,3/2] RISC-V: sbi: remove sbi_ecall tracepoints"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 1.20 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T21:39:46Z

Patch 3: "[v2,3/2] RISC-V: sbi: remove sbi_ecall tracepoints"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 71.35 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T21:39:48Z

Patch 3: "[v2,3/2] RISC-V: sbi: remove sbi_ecall tracepoints"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.23 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T21:39:50Z

Patch 3: "[v2,3/2] RISC-V: sbi: remove sbi_ecall tracepoints"
kdoc
Desc: Detects for kdoc errors
Duration: 0.84 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T21:39:52Z

Patch 3: "[v2,3/2] RISC-V: sbi: remove sbi_ecall tracepoints"
module-param
Desc: Detect module_param changes
Duration: 0.25 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T21:39:53Z

Patch 3: "[v2,3/2] RISC-V: sbi: remove sbi_ecall tracepoints"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.22 seconds
Result: PASS

linux-riscv-bot · 2025-06-19T21:39:55Z

Patch 3: "[v2,3/2] RISC-V: sbi: remove sbi_ecall tracepoints"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.30 seconds
Result: PASS

Linux RISC-V bot and others added 4 commits June 12, 2025 20:20

Adding CI files

8023d1f

linux-riscv-bot force-pushed the workflow__riscv__fixes branch 2 times, most recently from 6ce2eef to b5ded79 Compare June 24, 2025 01:05

linux-riscv-bot closed this Jun 27, 2025

linux-riscv-bot deleted the pw973967 branch June 27, 2025 01:06

Conversation

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

linux-riscv-bot commented Jun 19, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone