linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Siewior <bigeasy@linutronix.de>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC] powerpc/boot: add kernel,end node to the cuboot target
Date: Thu, 25 Sep 2008 10:50:14 +0200	[thread overview]
Message-ID: <48DB50C6.3030003@linutronix.de> (raw)
In-Reply-To: <F7E012CB-5062-496D-BECC-4B9EAFBD4D75@kernel.crashing.org>

Kumar Gala wrote:
> I missing why you are doing this?  Do you plan on using it w/32-bit kexec?

Yes. I plan to kexec my mpc8544 board.

> 
> - k
Sebastian

  reply	other threads:[~2008-09-25  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 19:54 [RFC] powerpc/boot: add kernel,end node to the cuboot target Sebastian Siewior
2008-09-23 22:28 ` Kumar Gala
2008-09-25  8:50   ` Sebastian Siewior [this message]
2008-09-24  1:24 ` Milton Miller
2008-09-25  9:43   ` Sebastian Siewior
2008-09-29 20:04   ` Sebastian Siewior
2008-09-30  7:44     ` Milton Miller
2008-09-30 17:21       ` Sebastian Siewior
2008-10-01  5:33         ` Milton 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=48DB50C6.3030003@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).