public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: torvalds@linux-foundation.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Andi Kleen <ak@suse.de>,
	"Antonino A. Daplas" <adaplas@pol.net>,
	linux-kernel@vger.kernel.org
Subject: Could you please merge the x86_64 EFI boot support patchset?
Date: Mon, 12 Nov 2007 09:45:50 +0800	[thread overview]
Message-ID: <1194831950.17223.44.camel@caritas-dev.intel.com> (raw)

Hi, Linus,

Could you please merge the following patchset:

[PATCH 0/2 -v3] x86_64 EFI boot support
[PATCH 1/2 -v3] x86_64 EFI boot support: EFI frame buffer driver
[PATCH 2/2 -v3] x86_64 EFI boot support: EFI boot document

The patchset has been in -mm tree from 2.6.23-rc2-mm2 on. Andrew Moton
had suggested it to be merged into 2.6.24 during early merge window of
2.6.24. It was not merged because the 32-bit boot protocol had not been
done at that time.

Now, the 32-bit boot protocol has been merged into 2.6.24. And this
patch has been in x86 patch queue.

I know that it is a little late for this patchset to be merged into
2.6.24. But this patchset is very simple, just adds a framebuffer
driver, so it is impossible for this patchset to break anything. And
this patchset will be helpful for people have machine with UEFI 64
firmware instead of legacy BIOS.

Best Regards,
Huang Ying

             reply	other threads:[~2007-11-12  1:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12  1:45 Huang, Ying [this message]
2008-01-23  7:00 ` Could you please merge the x86_64 EFI boot support patchset? Paul Jackson
2008-01-23  7:26   ` Huang, Ying
2008-01-23  7:46     ` Paul Jackson
2008-01-23  8:07       ` Huang, Ying
2008-01-23 17:38         ` Paul Jackson

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=1194831950.17223.44.camel@caritas-dev.intel.com \
    --to=ying.huang@intel.com \
    --cc=adaplas@pol.net \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox