Re: [GIT PULL] tracing: Updates for 4.20 (or 5.0)

2018-10-31 Thread Steven Rostedt
On Tue, 30 Oct 2018 10:02:16 -0700 Linus Torvalds wrote: > As an explanation, the above kind of sucks. "SDT"? I had to look it > up. I added a note to the commit message, but please, don't use random > acronyms in kernel explanations unless they are industry-standard and > comprehensible to

Re: [GIT PULL] tracing: Updates for 4.20 (or 5.0)

2018-10-31 Thread Steven Rostedt
On Tue, 30 Oct 2018 10:02:16 -0700 Linus Torvalds wrote: > As an explanation, the above kind of sucks. "SDT"? I had to look it > up. I added a note to the commit message, but please, don't use random > acronyms in kernel explanations unless they are industry-standard and > comprehensible to

Re: [GIT PULL] tracing: Updates for 4.20 (or 5.0)

2018-10-30 Thread Linus Torvalds
On Tue, Oct 30, 2018 at 6:37 AM Steven Rostedt wrote: > > The biggest change here is the updates to kprobes Pulled. However, a little note: > - Added support for SDT in uprobes As an explanation, the above kind of sucks. "SDT"? I had to look it up. I added a note to the commit message, but

Re: [GIT PULL] tracing: Updates for 4.20 (or 5.0)

2018-10-30 Thread Linus Torvalds
On Tue, Oct 30, 2018 at 6:37 AM Steven Rostedt wrote: > > The biggest change here is the updates to kprobes Pulled. However, a little note: > - Added support for SDT in uprobes As an explanation, the above kind of sucks. "SDT"? I had to look it up. I added a note to the commit message, but

[GIT PULL] tracing: Updates for 4.20 (or 5.0)

2018-10-30 Thread Steven Rostedt
Linus, The biggest change here is the updates to kprobes Back in January I posted patches to create function based events. These were the events that you suggested I make to allow developers to easily create events in code where no trace event exists. After posting those changes for review, it

[GIT PULL] tracing: Updates for 4.20 (or 5.0)

2018-10-30 Thread Steven Rostedt
Linus, The biggest change here is the updates to kprobes Back in January I posted patches to create function based events. These were the events that you suggested I make to allow developers to easily create events in code where no trace event exists. After posting those changes for review, it