All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <ak@suse.de>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	akpm@linux-foundation.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -v7 0/3] x86 boot: 32-bit boot protocol
Date: Wed, 24 Oct 2007 09:04:07 +0800	[thread overview]
Message-ID: <1193187847.23935.95.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <471E7078.4050908@zytor.com>

On Tue, 2007-10-23 at 15:06 -0700, H. Peter Anvin wrote:
> Huang, Ying wrote:
> > This patch set defines a 32-bit boot protocol for x86 platform, adds
> > an extensible boot parameter passing mechanism, export the boot
> > parameters via sysfs.
> > 
> > The patch set has been tested against kernel of git version
> > v2.6.23-6623-g55b70a0 (with Rusty's git tree pulled) on x86_64 and
> > i386.
> > 
> > This patch set is based on the proposal of Peter Anvin.
> > 
> 
> Acked-by: H. Peter Anvin <hpa@zytor.com>
> 
> This patchset should spend a cycle in -mm before being merged, though.

Do you think it is possible that the 3rd patch of the patchset: document
for 32 bit boot protocol can be merged into upstream firstly? It has
been used by kexec/LinuxBIOS already and the EFI support patches depend
on it too.

Best Regards,
Huang Ying

  reply	other threads:[~2007-10-24  1:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23  8:06 [PATCH -v7 0/3] x86 boot: 32-bit boot protocol Huang, Ying
2007-10-23 22:06 ` H. Peter Anvin
2007-10-24  1:04   ` Huang, Ying [this message]
2007-10-24  1:15     ` H. Peter Anvin

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=1193187847.23935.95.camel@caritas-dev.intel.com \
    --to=ying.huang@intel.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.