linux-kernel - Re: [PATCH 2.6.21 1/3] x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070503131557.8f9b2ce1.randy.dunlap@oracle.com>
Date:	Thu, 3 May 2007 13:15:57 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	chandramouli narayanan <mouli@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org, ak@...e.de, akpm@...ux-foundation.org
Subject: Re: [PATCH 2.6.21 1/3] x86_64: EFI64 support

On Thu, 03 May 2007 12:20:30 -0700 chandramouli narayanan wrote:

> 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?

I guess that Edgar stopped pushing it.  Sometimes persistence is
required.

Linus said that the patch "looks fine per se",
  http://marc.info/?l=linux-kernel&m=115380564326171&w=2
but needs more testers.

Presumably you have done more testing.  :)

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/