All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Matt Fleming <mjf@gentoo.org>, Dave Airlie <airlied@gmail.com>
Subject: Re: [PATCH 0/3] [GIT PULL][2.6.31] ring-buffer/tracing: various fixes
Date: Thu, 6 Aug 2009 14:21:33 +0200	[thread overview]
Message-ID: <20090806122132.GA13995@elte.hu> (raw)
In-Reply-To: <20090806025206.306150861@goodmis.org>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> 
> Ingo,
> 
> Please pull the latest tip/tracing/urgent tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/urgent
> 
> 
> Steven Rostedt (3):
>       ring-buffer: fix check of try_to_discard result
>       ring-buffer: do not disable ring buffer on oops_in_progress
>       tracing: do not use functions starting with .L in recordmcount.pl
> 
> ----
>  kernel/trace/ring_buffer.c |    4 ++--
>  scripts/recordmcount.pl    |    5 ++++-
>  2 files changed, 6 insertions(+), 3 deletions(-)

Pulled, thanks Steve!

	Ingo

      parent reply	other threads:[~2009-08-06 12:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06  2:52 [PATCH 0/3] [GIT PULL][2.6.31] ring-buffer/tracing: various fixes Steven Rostedt
2009-08-06  2:52 ` [PATCH 1/3] ring-buffer: fix check of try_to_discard result Steven Rostedt
2009-08-06  2:52 ` [PATCH 2/3] ring-buffer: do not disable ring buffer on oops_in_progress Steven Rostedt
2009-08-06  2:52 ` [PATCH 3/3] tracing: do not use functions starting with .L in recordmcount.pl Steven Rostedt
2009-08-06  4:11 ` [PATCH 0/3] [GIT PULL][2.6.31] ring-buffer/tracing: various fixes Robert Richter
2009-08-06 12:22   ` Ingo Molnar
2009-08-06 19:12     ` Steven Rostedt
2009-08-06 12:21 ` Ingo Molnar [this message]

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=20090806122132.GA13995@elte.hu \
    --to=mingo@elte.hu \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjf@gentoo.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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.