linux-kernel - Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

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: <20080220142312.2b5fa44f@core>
Date:	Wed, 20 Feb 2008 14:23:12 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Tilman Schmidt <tilman@...p.cc>
Cc:	Gregory Nietsky <gregory@...worksentry.co.za>,
	Sam Ravnborg <sam@...nborg.org>,
	Andi Kleen <andi@...stfloor.org>, Greg KH <greg@...ah.com>,
	kkeil@...e.de, isdn4linux@...tserv.isdn4linux.de,
	linux-kernel@...r.kernel.org, Jeff Garzik <jeff@...zik.org>
Subject: Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

> mISDN has two problems, which are of course interrelated:
> 
> a) complete lack of documentation for the in-kernel driver interface
>     (equivalent of Documentation/isdn/INTERFACE)
> 
> b) still doesn't support all the hardware isdn4linux supports.
> 
> As long as those problems aren't solved, the old stuff cannot be removed.
> Perhaps merging the current state of mISDN into the -mm tree would help
> with this. Perhaps not.

It should get put into the -mm tree so it can be worked on, and if they
won't do that it should probably get binned and people them know what is
going on and can fix the existing isdn code.
--
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/