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: <20080219095423.GB4164@uranus.ravnborg.org>
Date:	Tue, 19 Feb 2008 10:54:23 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Gregory Nietsky <gregory@...worksentry.co.za>
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 11:25:06AM +0200, Gregory Nietsky wrote:
> ive been hackin away at mISDN for a while and use it with recent kernels 
>  2.6.2X and have a patch for 2.6.24 (move from semaphore to complition) 
> the distro we built is heavily reliant on mISDN (voip) i dont use the 
> isdn kernel drivers at all any longer.
> 
> im all for mISDN been mainlined into the kernel and the old stuff been 
> removed there could be users still it is marked as depricated and the 
> plan was with 2.6 to use mISDN from the start.

Great!

First step would be to send a properly splitted up patchset for review
if is is ready.
Release early - relase often is the best way.

I will do my best to review the bits I can help with.

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