linux-kernel - Re: [PATCH 0/3] gigaset fixes for 2.6.34-rc1

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: <201003151600.29048.isdn@linux-pingi.de>
Date:	Mon, 15 Mar 2010 16:00:29 +0100
From:	Karsten Keil <isdn@...ux-pingi.de>
To:	Tilman Schmidt <tilman@...p.cc>
Cc:	David Miller <davem@...emloft.net>, Hansjoerg Lipp <hjlipp@....de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	isdn4linux <isdn4linux@...tserv.isdn4linux.de>,
	i4ldeveloper <i4ldeveloper@...tserv.isdn4linux.de>,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] gigaset fixes for 2.6.34-rc1

On Sonntag, 14. März 2010 23:58:05 Tilman Schmidt wrote:
> Karsten, David,
> 
> following are three bugfix patches to the Gigaset driver which should
> still go into 2.6.34 if possible, and also into the 2.6.33 stable branch.

Ack for all

> 
> Thanks,
> Tilman
> 
> Tilman Schmidt (3):
>   gigaset: avoid registering CAPI driver more than once
>   gigaset: correct clearing of at_state strings on RING
>   gigaset: prune use of tty_buffer_request_room
> 
>  drivers/isdn/gigaset/capi.c      |   44
>  +++++++++++++++++++++---------------- drivers/isdn/gigaset/common.c    |  
>   6 +++-
>  drivers/isdn/gigaset/ev-layer.c  |   12 +++-------
>  drivers/isdn/gigaset/gigaset.h   |    6 +++-
>  drivers/isdn/gigaset/i4l.c       |   28 +++++++++++++++++-------
>  drivers/isdn/gigaset/interface.c |    1 -
>  6 files changed, 57 insertions(+), 40 deletions(-)
> 
--
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/