Re: [PATCH v3 1/8] scripts/sorttable: Handle RISC-V patchable ftrace entries

Hello:

This series was applied to riscv/linux.git (fixes)
by Paul Walmsley <[email protected]>:

On Tue,  9 Jun 2026 14:29:52 +0800 you wrote:
> RISC-V uses -fpatchable-function-entry=8,4 when the compressed ISA is
> enabled and -fpatchable-function-entry=4,2 otherwise. In both cases, the
> patchable NOP area starts 8 bytes before the function symbol address.
> The __mcount_loc entries therefore point at the patchable NOP area
> associated with a function, while nm reports the function symbol at the
> entry address used for the function range check.
> 
> [...]

Here is the summary with links:
  - [v3,1/8] scripts/sorttable: Handle RISC-V patchable ftrace entries
    https://git.kernel.org/riscv/c/57ad674d032b
  - [v3,2/8] riscv: stacktrace: Add frame record metadata
    (no matching commit)
  - [v3,3/8] riscv: stacktrace: disable KASAN and KCOV instrumentation for stacktrace.o
    (no matching commit)
  - [v3,4/8] riscv: ftrace: always preserve s0 in dynamic ftrace register frame
    (no matching commit)
  - [v3,5/8] riscv: stacktrace: introduce stack-bound tracking helpers
    (no matching commit)
  - [v3,6/8] riscv: stacktrace: switch to frame-pointer based unwinder
    (no matching commit)
  - [v3,7/8] riscv: Kconfig: enable HAVE_RELIABLE_STACKTRACE and HAVE_LIVEPATCH
    (no matching commit)
  - [v3,8/8] selftests/livepatch: Add RISC-V syscall wrapper prefix
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html