linux-kernel - Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.

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]

Date:	Wed, 21 Feb 2007 00:12:28 +0100
From:	Tilman Schmidt <tilman@...p.cc>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
CC:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	Roman Zippel <zippel@...ux-m68k.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.

Am 20.02.2007 23:52 schrieb Robert P. J. Day:
> "deprecated" means that there *is* a complete replacement available
> *right now* and you should consider switching to it.
> 
> if you can't offer someone a completely functional, better alternative
> to what they're using now, then you can't say that what they're using
> now is deprecated.

So, to take a specific example (incidentally the one I am
personally interested in):

isdn4linux (CONFIG_ISDN_I4L), currently marked as "obsolete"
(which is undoubtedly incorrect), would not even qualify as
"deprecated" as long as its successor, the CAPI 2.0 subsystem
(CONFIG_ISDN_CAPI) doesn't support all the hardware currently
supported by old i4l.

Or did I misunderstand something there?

Thanks,
Tilman

-- 
Tilman Schmidt                          E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


Download attachment "signature.asc" of type "application/pgp-signature" (254 bytes)