From: Steven Rostedt <rostedt@goodmis.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Li Zefan <lizf@cn.fujitsu.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH v2] tracing: Dump either the oops's cpu source or all cpus buffers
Date: Mon, 19 Apr 2010 15:00:43 -0400 [thread overview]
Message-ID: <1271703643.10448.2.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20100418192902.f3fad119.randy.dunlap@oracle.com>
On Sun, 2010-04-18 at 19:29 -0700, Randy Dunlap wrote:
> On Mon, 19 Apr 2010 03:15:40 +0200 Frederic Weisbecker wrote:
>
> > Documentation/kernel-parameters.txt | 6 +++-
> > Documentation/trace/ftrace.txt | 6 +++-
> > drivers/char/sysrq.c | 2 +-
> > include/linux/ftrace.h | 4 ++-
> > include/linux/kernel.h | 11 ++++++-
> > kernel/trace/trace.c | 51 ++++++++++++++++++++++++++--------
> > 6 files changed, 61 insertions(+), 19 deletions(-)
Frederic,
Send out v3 with Randy's updates and:
Acked-by: Steven Rostedt <rostedt@goodmis.org>
-- Steve
> >
> > diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> > index e4cbca5..f6c68e8 100644
> > --- a/Documentation/kernel-parameters.txt
> > +++ b/Documentation/kernel-parameters.txt
> > @@ -789,8 +789,12 @@ and is between 256 and 4096 characters. It is defined in the file
> > as early as possible in order to facilitate early
> > boot debugging.
> >
> >
next prev parent reply other threads:[~2010-04-19 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 20:50 [PATCH] tracing: Dump either the oops's cpu source or all cpus buffers Frederic Weisbecker
2010-04-19 1:15 ` [PATCH v2] " Frederic Weisbecker
2010-04-19 2:29 ` Randy Dunlap
2010-04-19 19:00 ` Steven Rostedt [this message]
2010-04-19 4:19 ` [PATCH] " David Miller
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=1271703643.10448.2.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=tglx@linutronix.de \
/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