netdev - Re: [PATCH 0/8] ISDN patches for net-next

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: <4FA867B1.9080003@imap.cc>
Date:	Tue, 08 May 2012 02:24:17 +0200
From:	Tilman Schmidt <tilman@...p.cc>
To:	Karsten Keil <isdn@...ux-pingi.de>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
CC:	Hansjoerg Lipp <hjlipp@....de>, Karsten Keil <keil@...systems.de>,
	i4ldeveloper@...tserv.isdn4linux.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/8] ISDN patches for net-next

On 26.04.2012 01:02, /me wrote:
> here's a series of eight patches to the Kernel CAPI subsystem and
> the Gigaset driver. Please consider for application to net-next.
> The first three should also go into -stable and are tagged accordingly.

Is there anything missing for these to be accepted into net-next?
Or should I just be patient?

Thanks,
Tilman

> Tilman Schmidt (8):
>       isdn/gigaset: ratelimit CAPI message dumps
>       isdn/gigaset: fix CAPI disconnect B3 handling
>       isdn/gigaset: improve error handling querying firmware version
>       isdn/gigaset: fix readability damage 
>       isdn/gigaset: internal function name cleanup
>       isdn/gigaset: unify function return values
>       isdn/capi: fix readability damage
>       isdn/capi: elliminate capincci_find() in non-middleware case

-- 
Tilman Schmidt                    E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


Download attachment "signature.asc" of type "application/pgp-signature" (263 bytes)