From: Karsten Keil <isdn@linux-pingi.de>
To: Tilman Schmidt <tilman@imap.cc>
Cc: David Miller <davem@davemloft.net>,
Hansjoerg Lipp <hjlipp@web.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
isdn4linux <isdn4linux@listserv.isdn4linux.de>,
i4ldeveloper <i4ldeveloper@listserv.isdn4linux.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] gigaset fixes for 2.6.34-rc1
Date: Mon, 15 Mar 2010 16:00:29 +0100 [thread overview]
Message-ID: <201003151600.29048.isdn@linux-pingi.de> (raw)
In-Reply-To: <cover.1268580322.git.tilman@imap.cc>
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(-)
>
next prev parent reply other threads:[~2010-03-15 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 22:58 [PATCH 0/3] gigaset fixes for 2.6.34-rc1 Tilman Schmidt
2010-03-14 22:58 ` [PATCH 3/3] gigaset: prune use of tty_buffer_request_room Tilman Schmidt
2010-03-14 22:58 ` [PATCH 2/3] gigaset: correct clearing of at_state strings on RING Tilman Schmidt
2010-03-14 22:58 ` [PATCH 1/3] gigaset: avoid registering CAPI driver more than once Tilman Schmidt
2010-03-15 15:00 ` Karsten Keil [this message]
2010-03-15 23:06 ` [PATCH 0/3] gigaset fixes for 2.6.34-rc1 David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201003151600.29048.isdn@linux-pingi.de \
--to=isdn@linux-pingi.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=hjlipp@web.de \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tilman@imap.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).