public inbox for linux-kernel@vger.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>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/2] [GIT PULL][v3.0] tracing: Add refcount for system filter and enable
Date: Thu, 7 Jul 2011 16:15:25 +0200	[thread overview]
Message-ID: <20110707141525.GA19193@elte.hu> (raw)
In-Reply-To: <20110706211931.764277374@goodmis.org>


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

> 
> Ingo,
> 
> Please pull the latest tip/perf/urgent tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/perf/urgent
> 
> Head SHA1: 57f124ca21d216fca3ba3995235c15855f9b9980
> 
> 
> Steven Rostedt (2):
>       tracing: Add ref_count to event systems for freeing
>       tracing: Have enable system events use the subsystem_open routine
> 
> ----
>  kernel/trace/trace.h               |    1 +
>  kernel/trace/trace_events.c        |  113 ++++++++++++++++++++++++++++++------
>  kernel/trace/trace_events_filter.c |    6 ++
>  3 files changed, 102 insertions(+), 18 deletions(-)

Hm, i'm wondering, when was this bug introduced?

Thanks,

	Ingo

  parent reply	other threads:[~2011-07-07 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 21:19 [PATCH 0/2] [GIT PULL][v3.0] tracing: Add refcount for system filter and enable Steven Rostedt
2011-07-06 21:19 ` [PATCH 1/2] tracing: Add ref_count to event systems for freeing Steven Rostedt
2011-07-06 21:19 ` [PATCH 2/2] tracing: Have enable system events use the subsystem_open routine Steven Rostedt
2011-07-07 14:15 ` Ingo Molnar [this message]
2011-07-07 14:23   ` [PATCH 0/2] [GIT PULL][v3.0] tracing: Add refcount for system filter and enable 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=20110707141525.GA19193@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