From: Andi Kleen <ak@suse.de>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
akpm@linux-foundation.org, Yinghai Lu <yhlu.kernel@gmail.com>,
Chandramouli Narayanan <mouli@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC -mm 0/2] i386/x86_64 boot: 32-bit boot protocol
Date: Mon, 17 Sep 2007 16:30:17 +0200 [thread overview]
Message-ID: <200709171630.18066.ak@suse.de> (raw)
In-Reply-To: <1190018855.5866.27.camel@caritas-dev.intel.com>
> The real contents of 32-bit boot protocol patch is is in another 2 mails
> with the title:
>
> [RFC -mm 1/2] i386/x86_64 boot: setup data
> [RFC -mm 2/2] i386/x86_64 boot: document for 32 bit boot protocol
>
> The EFI patch in this mail is just an example of 32-bit boot protocol
> usage.
Please write meaningfull descriptions for each patch then. Just duplicating
the same in each is pretty useless.
-Andi
prev parent reply other threads:[~2007-09-17 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 8:26 [RFC -mm 0/2] i386/x86_64 boot: 32-bit boot protocol Huang, Ying
2007-09-17 8:40 ` Andi Kleen
2007-09-17 8:47 ` Huang, Ying
2007-09-17 14:30 ` Andi Kleen [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=200709171630.18066.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mouli@linux.intel.com \
--cc=yhlu.kernel@gmail.com \
--cc=ying.huang@intel.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