Re: [PATCH 0/2] [GIT PULL] tracing: More fixes for 4.20

2018-11-30 Thread Steven Rostedt
On Fri, 30 Nov 2018 10:56:06 -0800 Linus Torvalds wrote: > This way I got the matching diffstat from your pull requests, but more > importantly also the independent merge messages. > > The history looks slightly odd this way (with two adjacent merges of > continuous history), but I thought I'd e

Re: [PATCH 0/2] [GIT PULL] tracing: More fixes for 4.20

2018-11-30 Thread Linus Torvalds
On Fri, Nov 30, 2018 at 9:41 AM Linus Torvalds wrote: > > I went back and merged things [..] Note that I did this as two merges, even if one would have done (since the second pull request was just adding new commits on top of the first). This way I got the matching diffstat from your pull reques

Re: [PATCH 0/2] [GIT PULL] tracing: More fixes for 4.20

2018-11-30 Thread Steven Rostedt
On Fri, 30 Nov 2018 09:41:00 -0800 Linus Torvalds wrote: > On Thu, Nov 29, 2018 at 7:19 PM Steven Rostedt wrote: > > > > Note, this is on top of a previous git pull that I have submitted: > > > > http://lkml.kernel.org/r/20181127224031.76681...@vmware.local.home > > Hmm. > > I had dismisse

Re: [PATCH 0/2] [GIT PULL] tracing: More fixes for 4.20

2018-11-30 Thread Linus Torvalds
On Thu, Nov 29, 2018 at 7:19 PM Steven Rostedt wrote: > > Note, this is on top of a previous git pull that I have submitted: > > http://lkml.kernel.org/r/20181127224031.76681...@vmware.local.home Hmm. I had dismissed that, because the patch descriptors for that series had had "for-next" in the

[PATCH 0/2] [GIT PULL] tracing: More fixes for 4.20

2018-11-29 Thread Steven Rostedt
Linus, This includes two more fixes: - Change idx variable in DO_TRACE macro to __idx to avoid name conflicts. A kvm event had "idx" as a parameter and it confused the macro. - Fix a race where interrupts would be traced when set_graph_function was set. The previous patch set increased