linux-kernel - Re: [patch 0/6] x86: apicdef.h unification

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: <20071108102411.GG20836@erda.amd.com>
Date:	Thu, 8 Nov 2007 11:24:11 +0100
From:	"Robert Richter" <robert.richter@....com>
To:	"Thomas Gleixner" <tglx@...utronix.de>
cc:	"Ingo Molnar" <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
	"LKML" <linux-kernel@...r.kernel.org>
Subject: Re: [patch 0/6] x86: apicdef.h unification

Thomas,

On 06.11.07 21:32:12, Thomas Gleixner wrote:
> Thanks for doing this, but please check the x86 git repository
> (cleanup / mm branch) for stuff which has been worked on already.
> 
> Maybe we need some coordination for this.

Is it for sure that the x86/cleanup tree will go upstream soon and the
source will not change as much? The question is what code base to use
for new patches? I want to keep the porting effort as small as
possible.

-Robert

-- 
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@....com


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