From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/5] [GIT PULL] tracing: A few fixes and a clean up
Date: Fri, 22 Jun 2018 21:20:35 -0400 [thread overview]
Message-ID: <20180623012035.763099123@goodmis.org> (raw)
Linus,
This contains a few fixes and a clean up.
- A bad merge caused an "endif" to go in the wrong place in
scripts/Makefile.build
- Softirq tracing fix for tracing that corrupts lockdep and causes a false
splat
- Histogram documentation typo fixes
- Fix a bad memory reference when passing in no filter to the filter code
- Simplify code by using the swap macro instead of open coding the swap
Please pull the latest trace-v4.18-rc1 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.18-rc1
Tag SHA1: 50d890b32aae88f43b04fe477d9a00db564e78e9
Head SHA1: ed7d40bc67b8353c677b38c6cdddcdc310c0f452
Greg Thelen (1):
tracing: Fix SKIP_STACK_VALIDATION=1 build due to bad merge with -mrecord-mcount
Gustavo A. R. Silva (1):
tracing: Use swap macro in update_max_tr
Joel Fernandes (Google) (2):
softirq: Reorder trace_softirqs_on to prevent lockdep splat
tracing: Fix some errors in histogram documentation
Steven Rostedt (VMware) (1):
tracing: Check for no filter when processing event filters
----
Documentation/trace/histogram.txt | 23 ++++++++++++-----------
kernel/softirq.c | 6 +++++-
kernel/trace/trace.c | 6 +-----
kernel/trace/trace_events_filter.c | 10 +++++++++-
scripts/Makefile.build | 2 +-
5 files changed, 28 insertions(+), 19 deletions(-)
reply other threads:[~2018-06-23 1:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180623012035.763099123@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox