Thread (44 messages) 44 messages, 6 authors, 12d ago

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

From: Steven Rostedt <rostedt@goodmis.org>
Date: 2026-06-09 14:21:38
Also in: linux-kselftest, linux-perf-users, linux-riscv, live-patching, lkml

On Wed, 3 Jun 2026 10:10:44 +0800
Shuai Xue [off-list ref] wrote:
It's a pure comment cosmetic, not worth a respin on its own. But for the
I don't know. I've respinned for better comments before.
rest of the feedback on this series (the frame-record metadata contract
in patch 2 and the dead state->regs field / Call Trace output change in
patch 6) are the ones actually worth a new version.

Just to get the routing straight: are you planning to pick this one up
through the tracing tree on its own?

It feels like a good candidate for that -- it's an independent
regression fix (Fixes: 0ca1724b56af) that breaks *all* RISC-V dynamic
ftrace, not just livepatch, so it shouldn't have to wait on the rest of
the livepatch series.
As it affects RISCV and I don't have a RISCV to test, I would feel more
comfortable with it going through a RISCV tree that can test the patch.

Feel free to add:

Reviewed-by: Steven Rostedt <rostedt@goodmis.org>

-- Steve
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help