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]

Date:	Tue, 19 Feb 2008 10:40:34 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	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] ...

On Tue, Feb 19, 2008 at 09:50:33AM +0100, Sam Ravnborg wrote:
> Only issue seems that this large ISDN user base is not very active
> in respect to Linux driver development.

They don't need to because this stuff basically works and there isn't
much new hardware anymore and no new standards and it also doesn't really
need much tuning.

Or rather the new hardware development (like Asterisk support etc.) 
seemed to be mostly done on out of tree mISDN.

> If noone in the isdn community step up and take some responsibility
> for the current isdn drivers in Linux then we should just delete them.

So you're saying anything that has no active maintainer should 
be immediately deleted?

I suspect after you would be done with that a lot of (working) code in Linux
would be gone. 

-Andi

--
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/