From: David Miller <davem@davemloft.net>
To: tilman@imap.cc
Cc: isdn@linux-pingi.de, hjlipp@web.de, keil@b1-systems.de,
i4ldeveloper@listserv.isdn4linux.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/5] late Gigaset fixes for 2.6.35
Date: Fri, 25 Jun 2010 21:31:28 -0700 (PDT) [thread overview]
Message-ID: <20100625.213128.220048816.davem@davemloft.net> (raw)
In-Reply-To: <20100622-patch-gigaset-00.tilman@imap.cc>
From: Tilman Schmidt <tilman@imap.cc>
Date: Tue, 22 Jun 2010 01:54:04 +0200 (CEST)
> following are five patches to the Gigaset driver fixing reported
> problems with two CAPI applications (Asterisk and capifax). They
> fix serious bugs, though not technically regressions, and I would
> therefore appreciate if they could still make it into release
> 2.6.35.
All applied to net-2.6, thanks.
prev parent reply other threads:[~2010-06-26 4:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 23:54 [PATCH 0/5] late Gigaset fixes for 2.6.35 Tilman Schmidt
2010-06-21 23:54 ` [PATCH 1/5] isdn/gigaset: honor CAPI application's buffer size request Tilman Schmidt
2010-06-21 23:54 ` [PATCH 2/5] isdn/gigaset: correct CAPI voice connection encoding Tilman Schmidt
2010-06-21 23:54 ` [PATCH 3/5] isdn/gigaset: correct CAPI DATA_B3 Delivery Confirmation Tilman Schmidt
2010-06-21 23:55 ` [PATCH 4/5] isdn/gigaset: encode HLC and BC together Tilman Schmidt
2010-06-21 23:55 ` [PATCH 5/5] isdn/gigaset: correct CAPI connection state storage Tilman Schmidt
2010-06-22 4:02 ` [stable] [PATCH 0/5] late Gigaset fixes for 2.6.35 Greg KH
2010-06-26 4:31 ` David Miller [this message]
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=20100625.213128.220048816.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hjlipp@web.de \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=isdn@linux-pingi.de \
--cc=keil@b1-systems.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@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).