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: <alpine.DEB.2.02.1402061430420.29446@chino.kir.corp.google.com>
Date:	Thu, 6 Feb 2014 14:31:55 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Andi Kleen <andi@...stfloor.org>
cc:	Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [patch 1/4] x86, apic: Only use default_wait_for_init_deassert

On Thu, 6 Feb 2014, Andi Kleen wrote:

> > es7000_wait_for_init_deassert() is functionally equivalent to 
> > default_wait_for_init_deassert(), so remove the duplicate code and use
> > only a single function.
> 
> It would surprise me if anyone uses the es7000 anymore -- it may be
> reasonable to just deprecate the complete port.
> 

How do we usually do that?  Do we add a big fat warning for anyone who is 
using it for a few releases or just yank support out entirely and see if 
we're surprised?
--
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