| 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: <20070115172912.GA3323@pingi.kke.suse.de> Date: Mon, 15 Jan 2007 18:29:12 +0100 From: Karsten Keil <kkeil@...e.de> To: "Robert P. J. Day" <rpjday@...dspring.com> Cc: Tilman Schmidt <tilman@...p.cc>, Linux kernel mailing list <linux-kernel@...r.kernel.org>, kkeil@...e.de Subject: Re: any value to fixing apparent bugs in old ISDN4Linux? On Mon, Jan 15, 2007 at 12:17:37PM -0500, Robert P. J. Day wrote: > On Mon, 15 Jan 2007, Tilman Schmidt wrote: > > > Robert P. J. Day schrieb: > > > OTOH, since that code *is* in the allegedly obsolete old ISDN4Linux > > > code, perhaps that entire part of the tree can just be junked. but if > > > it's sticking around, it should probably be fixed. > > > > Please do not remove isdn4linux just yet. It's true that it has been > > marked as obsolete for quite some time, but it's still needed > > anyway. Its designated successor, the CAPI subsystem, so far only > > supports a very limited range of hardware. Dropping isdn4linux now > > would leave the owners of some very popular ISDN cards out in the > > cold. > > that wouldn't be my decision, i just made a note of an oddity. but if > it's still in actual use, then it really should be re-labelled from > "obsolete" to "deprecated," no? > Good point. -- Karsten Keil SuSE Labs ISDN development - 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