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: <49FB23E4.2030900@zytor.com>
Date:	Fri, 01 May 2009 09:31:32 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Sam Ravnborg <sam@...nborg.org>
CC:	Ingo Molnar <mingo@...e.hu>, Tim Abbott <tabbott@....EDU>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Anders Kaseorg <andersk@....EDU>,
	Waseem Daher <wdaher@....EDU>,
	Denys Vlasenko <vda.linux@...glemail.com>,
	Jeff Arnold <jbarnold@....EDU>, Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 00/11] section name cleanup for x86

Sam Ravnborg wrote:
> On Fri, May 01, 2009 at 01:58:49PM +0200, Ingo Molnar wrote:
>> * Tim Abbott <tabbott@....EDU> wrote:
>>
>>> This patch series cleans up the section names on the x86
>>> architecture.  It requires the architecture-independent macro
>>> definitions from this patch series:
>>>
>>> <http://www.spinics.net/lists/mips/msg33499.html>
>> Hm, we cannot pick the x86 bits up into the x86 tree without having 
>> these macros upstream first. So those macros need acks from Sam and 
>> maybe Linus will take them out of order. (they are pure additions so 
>> they look fairly safe and uncontroversial)
> 
> Thats the plan.
> 

By the way, I personally like the overall approach; I haven't studied
the patchset in detail yet, though.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ