Re: [PATCH bpf-next] bpf, tracing: unbreak lttng

From
Alexei Starovoitov <hidden>
Date
2018-03-26 22:26:23
Also in
linux-api
Reply to
Steven Rostedt, 2018-03-26
On 3/26/18 3:15 PM, Steven Rostedt wrote:
On Mon, 26 Mar 2018 15:08:45 -0700
Alexei Starovoitov [off-list ref] wrote:
quoted
for_each_kernel_tracepoint() is used by out-of-tree lttng module
and therefore cannot be changed.
Instead introduce kernel_tracepoint_find_by_name() to find
tracepoint by name.

Fixes: 9e9afbae6514 ("tracepoint: compute num_args at build time")
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
I'm curious, why can't you rebase? The first patch was never acked.
because I think it makes sense to keep such things in the commit log
and in the separate diff, so next developer is aware of what kind of
minefield the tracpoints are.
No wonder some maintainers refuse to add them.
Thread (9 messages) 9 messages, 4 authors, last reply 2018-03-27
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help