From: Simon Horman <horms@verge.net.au>
To: Zou Nan hai <nanhai.zou@intel.com>
Cc: kexec@lists.infradead.org,
Linux-IA64 <linux-ia64@vger.kernel.org>,
Vivek Goyal <vgoyal@in.ibm.com>,
fastboot <fastboot@lists.osdl.org>,
"Luck, Tony" <tony.luck@intel.com>
Subject: Re: kexec/kdump: Use generic elf code on ia64
Date: Tue, 08 May 2007 07:23:25 +0000 [thread overview]
Message-ID: <20070508072323.GB31881@verge.net.au> (raw)
In-Reply-To: <1178607344.2613.9.camel@linux-znh>
On Tue, May 08, 2007 at 02:55:44PM +0800, Zou Nan hai wrote:
> Hi,
> The patch looks ok to me.
> However split the patch in 2 parts,
> 1. Put pr_status to percpu data to save stack usage.
> 2. IA64 specific part.
> may help others to review the patches.
Sure, will do.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
prev parent reply other threads:[~2007-05-08 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 9:09 kexec/kdump: Use generic elf code on ia64 Simon Horman
2007-04-26 1:52 ` Simon Horman
2007-05-08 6:32 ` Simon Horman
2007-05-08 6:55 ` Zou Nan hai
2007-05-08 7:23 ` Simon Horman [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=20070508072323.GB31881@verge.net.au \
--to=horms@verge.net.au \
--cc=fastboot@lists.osdl.org \
--cc=kexec@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=nanhai.zou@intel.com \
--cc=tony.luck@intel.com \
--cc=vgoyal@in.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