From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/2] tracing: A couple more last minute fixes
Date: Wed, 06 Sep 2017 08:33:21 -0400 [thread overview]
Message-ID: <20170906123321.986503953@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 7685ab6c58557c6234f3540260195ecbee7fc4b3
Chunyu Hu (1):
tracing: Fix clear of RECORDED_TGID flag when disabling trace event
Steven Rostedt (VMware) (1):
tracing: Add barrier to trace_printk() buffer nesting modification
----
kernel/trace/trace.c | 8 +++++++-
kernel/trace/trace_events.c | 2 +-
2 files changed, 8 insertions(+), 2 deletions(-)
next reply other threads:[~2017-09-06 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 12:33 Steven Rostedt [this message]
2017-09-06 12:33 ` [for-next][PATCH 1/2] tracing: Add barrier to trace_printk() buffer nesting modification Steven Rostedt
2017-09-06 12:33 ` [for-next][PATCH 2/2] tracing: Fix clear of RECORDED_TGID flag when disabling trace event Steven Rostedt
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=20170906123321.986503953@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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