| 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
| ||
|
Message-Id: <200701172254.l0HMsDMK022934@turing-police.cc.vt.edu>
Date: Wed, 17 Jan 2007 17:54:13 -0500
From: Valdis.Kletnieks@...edu
To: "Robert P. J. Day" <rpjday@...dspring.com>
Cc: Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: "obsolete" versus "deprecated", and a new config option?
On Wed, 17 Jan 2007 17:04:20 EST, "Robert P. J. Day" said:
> > How much of the 'OBSOLETE' code should just be labelled 'BROKEN'
> > instead?
>
> the stuff that's actually "broken." :-)
Right - the question is how much code qualifies as either/both, and which
we should use when we encounter the random driver that's both obsolete
*and* broken...
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists