public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Horms <horms@verge.net.au>
To: "Zou, Nanhai" <nanhai.zou@intel.com>
Cc: Vivek Goyal <vgoyal@in.ibm.com>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Fastboot mailing list <fastboot@lists.osdl.org>,
	Morton Andrew Morton <akpm@osdl.org>,
	Mohan Kumar M <mohan@in.ibm.com>
Subject: Re: [PATCH] Kdump documentation update for 2.6.20
Date: Wed, 10 Jan 2007 10:53:34 +0900	[thread overview]
Message-ID: <20070110015333.GC21005@verge.net.au> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A086BA1@pdsmsx411.ccr.corp.intel.com>

On Wed, Jan 10, 2007 at 09:34:12AM +0800, Zou, Nanhai wrote:
> > >
> > > I am hoping it --args-linux will be required while loading vmlinux on
> > > IA64? Because this is ELF file specific option. And this interface should
> > > be common across all the architectures.
> > >
> > > > Then again, I could be wrong, I'm not sure that I understand
> > > > --args-linux, I just know that I'm not using it :)
> > 
> > I will take a look into this.
> > 
>  args-linux is not support by IA64 kdump. 
> To have common interface, maybe we should support it by ignore this
> arg like ppc does.

That sounds reasonable to me. Vivek, what do you think?

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/


  reply	other threads:[~2007-01-10  1:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08  7:58 [PATCH] Kdump documentation update for 2.6.20 Vivek Goyal
2007-01-09  1:18 ` Horms
2007-01-09 14:47   ` Vivek Goyal
2007-01-10  0:31     ` Horms
2007-01-10  1:34       ` Zou, Nanhai
2007-01-10  1:53         ` Horms [this message]
2007-01-10  4:43           ` Vivek Goyal
2007-01-10  5:37     ` Mohan Kumar M
2007-01-10  9:15       ` Vivek Goyal
2007-01-11  8:13         ` Horms

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=20070110015333.GC21005@verge.net.au \
    --to=horms@verge.net.au \
    --cc=akpm@osdl.org \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mohan@in.ibm.com \
    --cc=nanhai.zou@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