public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] tracing: some fixes for 2.6.31
Date: Mon, 15 Jun 2009 10:56:11 +0800	[thread overview]
Message-ID: <4A35B84B.40904@cn.fujitsu.com> (raw)

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(-)



             reply	other threads:[~2009-06-15  2:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15  2:56 Li Zefan [this message]
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 ` [PATCH 0/4] tracing: some fixes for 2.6.31 Frederic Weisbecker
2009-06-15 12:48   ` 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=4A35B84B.40904@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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