linux-kernel - Re: [PATCH 0/5] Clean up x86 CPU auto-loading

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: <20120213222607.GA19465@kroah.com>
Date:	Mon, 13 Feb 2012 14:26:07 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Thomas Renninger <trenn@...e.de>,
	Ben Hutchings <ben@...adent.org.uk>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	Andi Kleen <ak@...ux.intel.com>, linux-kernel@...r.kernel.org,
	Len Brown <lenb@...nel.org>, linux-pm@...r.kernel.org,
	Dave Jones <davej@...hat.com>, cpufreq@...r.kernel.org
Subject: Re: [PATCH 0/5] Clean up x86 CPU auto-loading

On Sun, Feb 12, 2012 at 05:26:44PM -0800, H. Peter Anvin wrote:
> On 02/12/2012 03:10 PM, Thomas Renninger wrote:
> > On Saturday 11 February 2012 23:44:16 Ben Hutchings wrote:
> >> This series fixes a number of apparent bugs in the recent changes to
> >> enable auto-loading by x86 CPU ID.
> > 
> > These all look correct.
> > I should have spotted the intel_idle modifications myself.
> > Good catch(es).
> > 
> > Greg: I expect these should get queued in your driver-core-next branch?
> > 
> 
> Either that or we can carry them in -tip as x86 patches, since there
> isn't a pending conflict this time.

Ok, if there are no dependancies on the driver-core-next tree, please
take this through the x86 trees.

thanks,

greg k-h
--
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/