public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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/3] tracing: Small improvements for 4.14
Date: Fri, 01 Sep 2017 07:03:05 -0400	[thread overview]
Message-ID: <20170901110305.527102517@goodmis.org> (raw)

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next

Head SHA1: 2a5bfe47624bfc835aa0632a0505ba55576c98db


Steven Rostedt (VMware) (2):
      tracing: Only have rmmod clear buffers that its events were active in
      ftrace: Zero out ftrace hashes when a module is removed

Zev Weiss (1):
      ftrace: Fix debug preempt config name in stack_tracer_{en,dis}able

----
 include/linux/ftrace.h       |  4 +--
 include/linux/trace_events.h |  8 +++---
 kernel/trace/ftrace.c        | 58 +++++++++++++++++++++++++++++++++++++++++---
 kernel/trace/trace.c         |  3 +++
 kernel/trace/trace.h         |  1 +
 kernel/trace/trace_events.c  | 15 ++++++------
 6 files changed, 71 insertions(+), 18 deletions(-)

             reply	other threads:[~2017-09-01 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 11:03 Steven Rostedt [this message]
2017-09-01 11:03 ` [for-next][PATCH 1/3] ftrace: Fix debug preempt config name in stack_tracer_{en,dis}able Steven Rostedt
2017-09-01 11:03 ` [for-next][PATCH 2/3] tracing: Only have rmmod clear buffers that its events were active in Steven Rostedt
2017-09-01 11:03 ` [for-next][PATCH 3/3] ftrace: Zero out ftrace hashes when a module is removed 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=20170901110305.527102517@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