public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Fastboot] [PATCH]send slave cpus to SAL slave loop on crash (IA64)
Date: Tue, 12 Dec 2006 09:31:57 +0000	[thread overview]
Message-ID: <20061212093156.GM18377@verge.net.au> (raw)
In-Reply-To: <20061201060852.GA13622@verge.net.au>

On Fri, Dec 01, 2006 at 03:08:53PM +0900, Horms wrote:
> On Tue, Nov 21, 2006 at 07:13:56AM +0800, Zou Nan hai wrote:
> > This patch make normal "kexec -l" first try physical address suggested
> > by vmlinux. 
> > 
> > If there is no enough memory, kexec tools will search /proc/iomem and
> > find a place to put the new kernel.
> > 
> > This is necessary for "kexec -l" to work on SN platform.
> > 
> > Signed-off-by: Zou Nan hai <nanhai.zou@intel.com>
> > 
> 
> Hi Nan hai, 
> 
> sorry for not responding sooner.
> 
> I have take a look at your patch with an eye to including it into 
> kexec-tools-testing. It does seem like a good feature.
> 
> Below is an updated version of the patch that cleans up your
> implementation a little. In particular.
> 
> * update_loaded_segments() returns -1 on error, 0 on success
>   - amongst other things the previous incarnation could return nothing
>     at all in once case.
> * else { if () { ; } } -> else if () { ; }
> * < 80 columns wide
> * removed trailing whitespace
> 
> Is it ok to apply this incarntation of the patch?
> I can make my changes a second patch if you prefer.
> 
> Signed-off-by: Simon Horman <horms@verge.net.au>

Hi,

I have applied your patch, and then my changes as a second patch
to kexec-tools-testing.

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


      reply	other threads:[~2006-12-12  9:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01  6:08 [Fastboot] [PATCH]send slave cpus to SAL slave loop on crash (IA64) Horms
2006-12-12  9:31 ` Horms [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=20061212093156.GM18377@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-ia64@vger.kernel.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