This should be a part of [3/5], because when bisecting, the test will check the README file and check the feature.
Thank you, On Sun, 5 Oct 2025 08:46:56 +0900 Ryan Chung <[email protected]> wrote: > Signed-off-by: Ryan Chung <[email protected]> > --- > kernel/trace/trace.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c > index b3c94fbaf002..ac0d3acc337e 100644 > --- a/kernel/trace/trace.c > +++ b/kernel/trace/trace.c > @@ -5524,7 +5524,8 @@ static const char readme_msg[] = > "\t r[maxactive][:[<group>/][<event>]] <place> [<args>]\n" > #endif > #ifdef CONFIG_FPROBE_EVENTS > - "\t f[:[<group>/][<event>]] <func-name>[%return] [<args>]\n" > + "\t f[:[<group>/][<event>]] <func-name>[:entry|:exit] > [<args>]\n" > + "\t (single symbols still accept %return)\n" > "\t t[:[<group>/][<event>]] <tracepoint> [<args>]\n" > #endif > #ifdef CONFIG_HIST_TRIGGERS > -- > 2.43.0 > -- Masami Hiramatsu (Google) <[email protected]>
