Skip to content

[PW_SID:1155804] clocksource/timer-riscv: use riscv_has_extension_likely - #2570

Closed
linux-riscv-bot wants to merge 2 commits into
workflow__riscv__fixesfrom
pw1155804
Closed

[PW_SID:1155804] clocksource/timer-riscv: use riscv_has_extension_likely#2570
linux-riscv-bot wants to merge 2 commits into
workflow__riscv__fixesfrom
pw1155804

Conversation

@linux-riscv-bot

Copy link
Copy Markdown

PR for series 1155804 applied to workflow__riscv__fixes

Name: clocksource/timer-riscv: use riscv_has_extension_likely
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=1155804
Version: 1

Linux RISC-V bot and others added 2 commits September 2, 2026 05:24
Instead of static branch, use riscv_has_extension_likely() to check
whether SSTC is supported or not. For one thing, this is straight
forward, no need to add and enable/disable a static branch during
probe; For another, riscv_has_extension_likely() is based on
alternative mechanism, it avoid some downsides of static branch, for
example static branch's metadata in the __jump_table section, which is
not discarded after ISA extensions are finalized, wastes some space.

Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
@linux-riscv-bot

Copy link
Copy Markdown
Author

Patch 1: "clocksource/timer-riscv: use riscv_has_extension_likely"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 143.62 seconds
Result: PASS

@linux-riscv-bot

Copy link
Copy Markdown
Author

Patch 1: "clocksource/timer-riscv: use riscv_has_extension_likely"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 1473.88 seconds
Result: PASS

@linux-riscv-bot

Copy link
Copy Markdown
Author

Patch 1: "clocksource/timer-riscv: use riscv_has_extension_likely"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1814.67 seconds
Result: PASS

@linux-riscv-bot

Copy link
Copy Markdown
Author

Patch 1: "clocksource/timer-riscv: use riscv_has_extension_likely"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 27.04 seconds
Result: PASS

@linux-riscv-bot

Copy link
Copy Markdown
Author

Patch 1: "clocksource/timer-riscv: use riscv_has_extension_likely"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 27.79 seconds
Result: PASS

@linux-riscv-bot

Copy link
Copy Markdown
Author

Patch 1: "clocksource/timer-riscv: use riscv_has_extension_likely"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 0.72 seconds
Result: PASS

@linux-riscv-bot

Copy link
Copy Markdown
Author

Patch 1: "clocksource/timer-riscv: use riscv_has_extension_likely"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 91.12 seconds
Result: PASS

@linux-riscv-bot

Copy link
Copy Markdown
Author

Patch 1: "clocksource/timer-riscv: use riscv_has_extension_likely"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.23 seconds
Result: PASS

@linux-riscv-bot

Copy link
Copy Markdown
Author

Patch 1: "clocksource/timer-riscv: use riscv_has_extension_likely"
kdoc
Desc: Detects for kdoc errors
Duration: 0.85 seconds
Result: PASS

@linux-riscv-bot

Copy link
Copy Markdown
Author

Patch 1: "clocksource/timer-riscv: use riscv_has_extension_likely"
module-param
Desc: Detect module_param changes
Duration: 0.24 seconds
Result: PASS

@linux-riscv-bot

Copy link
Copy Markdown
Author

Patch 1: "clocksource/timer-riscv: use riscv_has_extension_likely"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.23 seconds
Result: PASS

@linux-riscv-bot

Copy link
Copy Markdown
Author

Patch 1: "clocksource/timer-riscv: use riscv_has_extension_likely"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.30 seconds
Result: PASS

@linux-riscv-bot
linux-riscv-bot deleted the pw1155804 branch September 2, 2026 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants