From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
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, 07 Jul 2011 10:23:28 -0400 [thread overview]
Message-ID: <1310048608.26417.204.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20110707141525.GA19193@elte.hu>
On Thu, 2011-07-07 at 16:15 +0200, Ingo Molnar wrote:
> * 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?
>
It was introduced a while ago, I believe by this commit:
commit dc82ec98a4727fd51b77e92d05fe7d2db3dcc11c
Date: Thu Jul 9 16:22:22 2009 +0800
tracing/filter: Remove empty subsystem and its directory
-- Steve
prev parent reply other threads:[~2011-07-07 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 21:19 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 ` [PATCH 0/2] [GIT PULL][v3.0] tracing: Add refcount for system filter and enable Ingo Molnar
2011-07-07 14:23 ` Steven Rostedt [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=1310048608.26417.204.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®