From: chandramouli narayanan <mouli@linux.intel.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, ak@suse.de, akpm@linux-foundation.org
Subject: Re: [PATCH 2.6.21 1/3] x86_64: EFI64 support
Date: Thu, 03 May 2007 12:20:30 -0700 [thread overview]
Message-ID: <463A35FE.3080501@linux.intel.com> (raw)
In-Reply-To: <20070502195635.6fcc59d6.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> Can you share EFI code as much as possible among ia64, i386,
> and x86_64 instead of duplicating it?
Hi Randy,
Based on the feedback from Andi and you, these are the areas:
1. conversion of EFI memory map to e820 map
2. Consolidation/sharing of efi code among the architectures.
3. Coding style violations/typos/clarity in comments.
First I apologize for the coding style violations where I should have
done better. I will fix these in the next patch.
I would like to address the above in stages with patch updates. This
will take me some time with the fixes and testing.
A while back, Edgar Hucek submitted a patch (probably 2.6.18 mm tree?)
for efi to e820 memory mapping for i386.I don't see this code in the
2.6.21 release which makes me wonder whether it was accepted and the
history behind it. Any pointers in this regard?
thanks
- mouli
next prev parent reply other threads:[~2007-05-03 19:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 18:59 [PATCH 2.6.21 0/3] x86_64: EFI64 support Chandramouli Narayanan
2007-05-01 18:59 ` [PATCH 2.6.21 1/3] " Chandramouli Narayanan
2007-05-03 2:56 ` Randy Dunlap
2007-05-03 19:20 ` chandramouli narayanan [this message]
2007-05-03 20:15 ` Randy Dunlap
2007-06-01 16:47 ` Yinghai Lu
2007-05-04 13:01 ` Andi Kleen
2007-05-25 22:46 ` chandramouli narayanan
2007-06-01 18:39 ` Eric W. Biederman
2007-06-01 18:44 ` Eric W. Biederman
2007-05-01 18:59 ` [PATCH 2.6.21 2/3] " Chandramouli Narayanan
2007-05-02 20:55 ` Andi Kleen
2007-05-02 22:43 ` chandramouli narayanan
2007-06-01 18:50 ` Eric W. Biederman
2007-05-01 18:59 ` [PATCH 2.6.21 3/3] " Chandramouli Narayanan
2007-06-01 18:52 ` Eric W. Biederman
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=463A35FE.3080501@linux.intel.com \
--to=mouli@linux.intel.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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