mirror of https://lore.kernel.org/lkml/
 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>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/2] [GIT PULL][v2.6.34] tracing: fixes
Date: Fri, 2 Apr 2010 22:07:23 +0200	[thread overview]
Message-ID: <20100402200722.GB4045@elte.hu> (raw)
In-Reply-To: <20100330025800.713540457@goodmis.org>


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

> Ingo,
> 
> I rebased my branch against yours and removed the module patch since it 
> looks like it is no longer urgent. I moved it over to my core branch along 
> with a fix to the compile error you saw with it. I'll be pushing that later 
> this week.
> 
> These two patchs still should go into 34.
> 
> 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
> 
> 
> Julia Lawall (1):
>       ring-buffer: Add missing unlock
> 
> Li Zefan (1):
>       tracing: Fix lockdep warning in global_clock()
> 
> ----
>  kernel/trace/ring_buffer.c |    8 +++++---
>  kernel/trace/trace_clock.c |    4 ++--
>  2 files changed, 7 insertions(+), 5 deletions(-)

Pulled, thanks Steve!

	Ingo

  parent reply	other threads:[~2010-04-02 20:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30  2:58 Steven Rostedt
2010-03-30  2:58 ` [PATCH 1/2] tracing: Fix lockdep warning in global_clock() Steven Rostedt
2010-03-30  2:58 ` [PATCH 2/2] ring-buffer: Add missing unlock Steven Rostedt
2010-04-02 20:07 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-03-25  1:02 [PATCH 0/2][GIT PULL][v2.6.34] tracing: 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=20100402200722.GB4045@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®