linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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/3] [GIT PULL] tracing: Minor fixes for 4.14 (and stable)
Date: Wed, 20 Sep 2017 09:29:38 -0400	[thread overview]
Message-ID: <20170920132938.098873640@goodmis.org> (raw)


Linus,

This includes 3 minor fixes.

 - Have writing to trace file clear the irqsoff (and friends) tracer

 - trace_pipe behavior for instance buffers was different than top buffer

 - Show a message of why mmiotrace doesn't start from commandline

Please pull the latest trace-v4.14-rc1 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.14-rc1

Tag SHA1: cd68d5e5af1d4b58d32f937d7a59d15e88de3e4e
Head SHA1: 75df6e688ccd517e339a7c422ef7ad73045b18a2


Bo Yan (1):
      tracing: Erase irqsoff trace with empty write

Tahsin Erdogan (1):
      tracing: Fix trace_pipe behavior for instance traces

Ziqian SUN (Zamir) (1):
      tracing: Ignore mmiotrace from kernel commandline

----
 kernel/trace/trace.c           | 19 ++++++++++++++++---
 kernel/trace/trace.h           |  2 ++
 kernel/trace/trace_mmiotrace.c |  1 +
 3 files changed, 19 insertions(+), 3 deletions(-)

             reply	other threads:[~2017-09-20 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 13:29 Steven Rostedt [this message]
2017-09-20 13:29 ` [PATCH 1/3] tracing: Erase irqsoff trace with empty write Steven Rostedt
2017-09-20 13:29 ` [PATCH 2/3] tracing: Ignore mmiotrace from kernel commandline Steven Rostedt
2017-09-20 13:29 ` [PATCH 3/3] tracing: Fix trace_pipe behavior for instance traces 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=20170920132938.098873640@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;
as well as URLs for NNTP newsgroup(s).