All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/6] [GIT PULL] tracing/ring-buffer: various fixes and cleanups
Date: Thu, 10 Sep 2009 00:12:19 -0400	[thread overview]
Message-ID: <20090910041219.149954890@goodmis.org> (raw)


Ingo,

Please pull the latest tip/tracing/core tree, which can be found at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/tracing/core


Li Zefan (4):
      tracing: remove dead code
      tracing: format clean ups
      tracing: remove stats from struct tracer
      tracing: move PRED macros to trace_events_filter.c

Robert Richter (1):
      ring-buffer: consolidate interface of rb_buffer_peek()

Steven Rostedt (1):
      tracing: do not grab lock in wakeup latency function tracing

----
 kernel/trace/ring_buffer.c         |   11 ++---
 kernel/trace/trace.h               |   86 +++++-------------------------------
 kernel/trace/trace_events_filter.c |   41 +++++++++++++++++
 kernel/trace/trace_sched_wakeup.c  |   36 +++++++++------
 4 files changed, 78 insertions(+), 96 deletions(-)
-- 

             reply	other threads:[~2009-09-10  4:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-10  4:12 Steven Rostedt [this message]
2009-09-10  4:12 ` [PATCH 1/6] ring-buffer: consolidate interface of rb_buffer_peek() Steven Rostedt
2009-09-10  4:12 ` [PATCH 2/6] tracing: do not grab lock in wakeup latency function tracing Steven Rostedt
2009-09-10  4:12 ` [PATCH 3/6] tracing: remove dead code Steven Rostedt
2009-09-10  4:12 ` [PATCH 4/6] tracing: format clean ups Steven Rostedt
2009-09-10  4:12 ` [PATCH 5/6] tracing: remove stats from struct tracer Steven Rostedt
2009-09-10  4:12 ` [PATCH 6/6] tracing: move PRED macros to trace_events_filter.c 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=20090910041219.149954890@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.