All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Pekka Paalanen <pq@iki.fi>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/3] ftrace: updates for 2.6.29
Date: Sun, 15 Feb 2009 20:07:31 +0100	[thread overview]
Message-ID: <20090215190731.GA10534@elte.hu> (raw)
In-Reply-To: <20090215205846.4d96260b@daedalus.pq.iki.fi>


* Pekka Paalanen <pq@iki.fi> wrote:

> On Sun, 11 Jan 2009 04:06:41 +0100
> Ingo Molnar <mingo@elte.hu> wrote:
> 
> > 
> > * Steven Rostedt <rostedt@goodmis.org> wrote:
> > 
> > > Ingo,
> > > 
> > > The following patches are in:
> > > 
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> > > 
> > >     branch: tip/devel
> > > 
> > > 
> > > Pekka Paalanen (3):
> > >       doc: mmiotrace.txt, buffer size control change
> > >       trace: mmiotrace to the tracer menu in Kconfig
> > >       mmiotrace: count events lost due to not recording
> > > 
> > > ----
> > >  Documentation/tracers/mmiotrace.txt |    6 ++----
> > >  arch/x86/Kconfig.debug              |   24 ++----------------------
> > >  kernel/trace/Kconfig                |   23 +++++++++++++++++++++++
> > >  kernel/trace/trace_mmiotrace.c      |   14 ++++++++++----
> > >  4 files changed, 37 insertions(+), 30 deletions(-)
> > 
> > pulled into tip/tracing/urgent, thanks Steve!
> 
> Hi,
> 
> I was just diffing linus/master to Ingo's tip/master, and I see the
> "mmiotrace: count events lost due to not recording" being added in
> tip/master. The doc and Kconfig updates also, nothing is in linus'.
> 
> I thought all these were going into 2.6.29. What happened?

The urgent marker got lost. [There were a bunch of changes originally
destined for .29 but then delayed to .30.]

I've queued them up for .29-rc6 into tip:tracing/urgent:

 [tracing/urgent 391b170] mmiotrace: count events lost due to not recording
 [tracing/urgent 6bc5c36] trace: mmiotrace to the tracer menu in Kconfig
 [tracing/urgent f9aa28a] doc: mmiotrace.txt, buffer size control change

It never hurts to double-check the routing and status of your commits.

Thanks,

	Ingo

      reply	other threads:[~2009-02-15 19:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09  0:27 [PATCH 0/3] ftrace: updates for 2.6.29 Steven Rostedt
2009-01-09  0:27 ` [PATCH 1/3] doc: mmiotrace.txt, buffer size control change Steven Rostedt
2009-01-09  0:27 ` [PATCH 2/3] trace: mmiotrace to the tracer menu in Kconfig Steven Rostedt
2009-01-09  0:27 ` [PATCH 3/3] mmiotrace: count events lost due to not recording Steven Rostedt
2009-01-09  1:10   ` Andrew Morton
2009-01-09  1:56     ` Steven Rostedt
2009-01-09 20:04 ` [PATCH 0/3] ftrace: updates for 2.6.29 Pekka Paalanen
2009-01-11  3:06 ` Ingo Molnar
2009-02-15 18:58   ` Pekka Paalanen
2009-02-15 19:07     ` 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=20090215190731.GA10534@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pq@iki.fi \
    --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.