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 17:14:36 +0100
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Sam Ravnborg <sam@...nborg.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] ...

Hi Andi,

>>>> 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?
>>
>> You do not recognize a provocation when you see it?
>> I wanted a reaction from the isdn community - and I got so.
>> So lets look forward.
>
> Well it was more a lie because you couldn't possibly make up to your
> threat anyways.
>
> I'm not sure either it's a good idea to try to merge mISDN if the
> maintainers don't think it is ready yet.

you can't wait until it is perfect. Then it never gets merged. The out- 
of-tree ISDN stuff has always been painful. And that was already in  
the ISDN4Linux days which were Linux 2.2 days or even earlier.

My proposal is to merge mISDN and then see what falls out. My guess it  
won't be that bad as everybody thinks and then we go from there. Next  
step is to remove ISDN4Linux since that should not be used at all  
anymore.

Regards

Marcel

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