From: Frederic Weisbecker <fweisbec@gmail.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] tracing: some fixes for 2.6.31
Date: Mon, 15 Jun 2009 14:21:55 +0200 [thread overview]
Message-ID: <20090615122152.GA6044@nowhere> (raw)
In-Reply-To: <4A35B84B.40904@cn.fujitsu.com>
On Mon, Jun 15, 2009 at 10:56:11AM +0800, Li Zefan wrote:
> Some small but not trival fixes for 2.6.31:
>
> [PATCH 1/4] tracing: fix a typo in tracing_cpumask_write()
> [PATCH 2/4] tracing: replace a GFP_ATOMIC with GFP_KERNEL allocation
> [PATCH 3/4] tracing/filters: operand can be negative
> [PATCH 4/4] tracing/filters: strloc should be unsigned short
> ---
> kernel/trace/trace.c | 8 ++++----
> kernel/trace/trace_events_filter.c | 9 +++++++--
> 2 files changed, 11 insertions(+), 6 deletions(-)
>
>
Acked-by: Frederic Weisbecker <fweisbec@gmail.com> for
the whole series. Thanks!
next prev parent reply other threads:[~2009-06-15 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 2:56 [PATCH 0/4] tracing: some fixes for 2.6.31 Li Zefan
2009-06-15 2:56 ` [PATCH 1/4] tracing: fix a typo in tracing_cpumask_write() Li Zefan
2009-06-15 18:13 ` [tip:tracing/urgent] " tip-bot for Li Zefan
2009-06-15 2:57 ` [PATCH 2/4] tracing: replace a GFP_ATOMIC with GFP_KERNEL allocation Li Zefan
2009-06-15 18:13 ` [tip:tracing/urgent] " tip-bot for Li Zefan
2009-06-15 2:58 ` [PATCH 3/4] tracing/filters: operand can be negative Li Zefan
2009-06-15 18:13 ` [tip:tracing/urgent] " tip-bot for Li Zefan
2009-06-15 2:59 ` [PATCH 4/4] tracing/filters: strloc should be unsigned short Li Zefan
2009-06-15 18:13 ` [tip:tracing/urgent] " tip-bot for Li Zefan
2009-06-15 12:21 ` Frederic Weisbecker [this message]
2009-06-15 12:48 ` [PATCH 0/4] tracing: some fixes for 2.6.31 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=20090615122152.GA6044@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--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