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@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/2] [GIT PULL] tracing: Minor fixes
Date: Wed, 20 Oct 2010 22:42:33 -0400	[thread overview]
Message-ID: <20101021024233.530237054@goodmis.org> (raw)


Ingo,

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

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


Steven Rostedt (2):
      tracing: Prevent unloadable modules from using trace_bprintk()
      tracing: Do not limit the size of the number of CPU buffers

----
 include/linux/kernel.h      |   21 +++++++++++++++++++--
 kernel/trace/trace.c        |    8 ++------
 kernel/trace/trace_printk.c |    2 ++
 3 files changed, 23 insertions(+), 8 deletions(-)

             reply	other threads:[~2010-10-21  2:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21  2:42 Steven Rostedt [this message]
2010-10-21  2:42 ` [PATCH 1/2] tracing: Prevent unloadable modules from using trace_bprintk() Steven Rostedt
2010-10-21  3:42   ` Frederic Weisbecker
2010-10-21  3:47     ` Steven Rostedt
2010-10-21  3:54       ` Frederic Weisbecker
2010-10-21  8:16   ` Ingo Molnar
2010-10-21 10:57     ` Steven Rostedt
2010-10-21 11:05       ` Ingo Molnar
2010-10-21  2:42 ` [PATCH 2/2] tracing: Do not limit the size of the number of CPU buffers Steven Rostedt
  -- strict thread matches above, loose matches on Subject: below --
2013-02-19  4:15 [PATCH 0/2] [GIT PULL] tracing: minor fixes Steven Rostedt
2018-05-04 15:52 [PATCH 0/2] [GIT PULL] tracing: Minor fixes 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=20101021024233.530237054@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox