From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Vinay Sridhar <vinay@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, ellerman@au1.ibm.com
Subject: Re: [PATCH] ppc64: xmon: Add dl command to dump contents of __log_buf
Date: Mon, 18 May 2009 13:29:33 +1000 [thread overview]
Message-ID: <1242617373.18075.26.camel@pasglop> (raw)
In-Reply-To: <200905151443.07723.vinay@linux.vnet.ibm.com>
On Fri, 2009-05-15 at 14:43 +0530, Vinay Sridhar wrote:
> Hello All,
>
> Quite a while back Michael Ellerman had posted a patch to add support to xmon to print the contents of the console log pointed to by __log_buf.
> Here's the link to that patch - http://ozlabs.org/pipermail/linuxppc64-dev/2005-March/003657.html
> I've ported the patch in the above link to 2.6.30-rc5 and have tested it.
Thanks, good idea.
I'll review & test and if all goes well, it will be in -next.
Cheers,
Ben
prev parent reply other threads:[~2009-05-18 3:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 9:13 [PATCH] ppc64: xmon: Add dl command to dump contents of __log_buf Vinay Sridhar
2009-05-18 3:29 ` Benjamin Herrenschmidt [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=1242617373.18075.26.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=ellerman@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=vinay@linux.vnet.ibm.com \
/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).