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>
Subject: Re: [PATCH 0/2] [GIT PULL][v3.2] tracing: various fixes
Date: Mon, 17 Oct 2011 20:54:41 +0200	[thread overview]
Message-ID: <20111017185440.GB5545@elte.hu> (raw)
In-Reply-To: <20111017174938.842273454@goodmis.org>


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

> 
> 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-trace.git
> tip/perf/core
> 
> Head SHA1: 436fc280261dcfce5af38f08b89287750dc91cd2
> 
> 
> Geunsik Lim (1):
>       ftrace: Fix README to state tracing_on to start/stop tracing
> 
> Steven Rostedt (1):
>       tracing: Fix returning of duplicate data after EOF in trace_pipe_raw
> 
> ----
>  kernel/trace/trace.c |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)

Pulled, thanks Steve.

How about the m32r build fix? I think we should apply it to perf/core 
if everyone else was fine with your fix.

Thanks,

	Ingo

  parent reply	other threads:[~2011-10-17 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 17:49 [PATCH 0/2] [GIT PULL][v3.2] tracing: various fixes Steven Rostedt
2011-10-17 17:49 ` [PATCH 1/2] ftrace: Fix README to state tracing_on to start/stop tracing Steven Rostedt
2011-10-17 17:49 ` [PATCH 2/2] tracing: Fix returning of duplicate data after EOF in trace_pipe_raw Steven Rostedt
2011-10-17 18:54 ` Ingo Molnar [this message]
2011-10-17 19:10   ` [PATCH 0/2] [GIT PULL][v3.2] tracing: various fixes Steven Rostedt
2011-10-17 19:40     ` Ingo Molnar
2011-10-17 20:05       ` Steven Rostedt
2011-10-17 20:12         ` Steven Rostedt
2011-10-17 21:26           ` David Rientjes
2011-10-18  0:09             ` Steven Rostedt
2011-10-18  3:16               ` Hirokazu Takata

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=20111017185440.GB5545@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --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 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.