From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>, Paul Mackerras <paulus@samba.org>
Subject: Re: [GIT PULL] tracing: Perf tracing fixes
Date: Sat, 3 Oct 2009 15:57:35 +0200 [thread overview]
Message-ID: <20091003135734.GB5617@nowhere> (raw)
In-Reply-To: <1254577650-5623-1-git-send-email-fweisbec@gmail.com>
On Sat, Oct 03, 2009 at 03:47:28PM +0200, Frederic Weisbecker wrote:
> Ingo,
>
> Please pull these .33 tracing fixes from
Hmm, now I realize this code is upstream already.
I should better rebase it against latest Linus's tree.
Sorry.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> tracing/core
>
> These address reviews from Paul mackerras.
>
> I also plan to rename the whole "ftrace event profile" naming to
> "ftrace event perf" soon.
>
> Thanks.
>
> Frederic Weisbecker (2):
> tracing: Check total refcount before releasing bufs in profile_enable failure
> tracing: Use free_percpu instead of kfree
>
> kernel/trace/trace_event_profile.c | 15 ++++++++++-----
> 1 files changed, 10 insertions(+), 5 deletions(-)
next prev parent reply other threads:[~2009-10-03 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 4:50 Possible bug in ftrace_profile_enable_event Paul Mackerras
2009-10-01 6:20 ` Steven Rostedt
2009-10-02 12:13 ` Frédéric Weisbecker
2009-10-03 13:47 ` [GIT PULL] tracing: Perf tracing fixes Frederic Weisbecker
2009-10-03 13:57 ` Frederic Weisbecker [this message]
2009-10-05 17:54 ` Frederic Weisbecker
2009-10-06 12:30 ` Ingo Molnar
2009-10-03 13:47 ` [PATCH 1/2] tracing: Check total refcount before releasing bufs in profile_enable failure Frederic Weisbecker
2009-10-07 3:08 ` Paul Mackerras
2009-10-08 21:43 ` Frederic Weisbecker
2009-10-08 21:53 ` Paul Mackerras
2009-10-03 13:47 ` [PATCH 2/2] tracing: Use free_percpu instead of kfree Frederic Weisbecker
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=20091003135734.GB5617@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).