linux-kernel - Re: [tip:x86/urgent] x86, amd-nb: Rename CPU PCI id define for F4

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] [day] [month] [year] [list]

Date:	Thu, 31 Mar 2011 18:28:18 +0200
From:	Borislav Petkov <bp@...64.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Ingo Molnar <mingo@...e.hu>, "mingo@...hat.com" <mingo@...hat.com>,
	"hpa@...or.com" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"bp@...64.org" <bp@...64.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"linux-tip-commits@...r.kernel.org" 
	<linux-tip-commits@...r.kernel.org>
Subject: Re: [tip:x86/urgent] x86, amd-nb: Rename CPU PCI id define for F4

On Thu, Mar 31, 2011 at 12:14:01PM -0400, Jesse Barnes wrote:
> > The new ID went upstream via cb293250c71f in the merge window, so i wanted to 
> > shorten the life-time of the obsoleted name - that will also reduce the chance 
> > of any conflicts.
> 
> Sounds good, thanks.

Yep, definitely a good idea since I have a couple of patches coming up
for the next merge window and they use this particular #define. That's
why I sent it out now, thinking it is trivial enough to go in and thus
to avoid conflicts at merge window time.

Thanks.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
--
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/