From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: tilman-ZTO5kqT2PaM@public.gmane.org
Cc: isdn-iHCpqvpFUx0uJkBD2foKsQ@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
isdn4linux-JX7+OpRa80SjiSfgN6Y1Ib39b6g2fGNp@public.gmane.org,
hjlipp-S0/GAf8tV78@public.gmane.org,
keil-shG/GajIFYqbacvFa/9K2g@public.gmane.org,
i4ldeveloper-JX7+OpRa80SjiSfgN6Y1Ib39b6g2fGNp@public.gmane.org
Subject: Re: [PATCH 00/11] Gigaset driver patches for 2.6.32 (v3)
Date: Tue, 06 Oct 2009 23:39:01 -0700 (PDT) [thread overview]
Message-ID: <20091006.233901.192206610.davem@davemloft.net> (raw)
In-Reply-To: <20091006-patch-gigaset-00.tilman-ZTO5kqT2PaM@public.gmane.org>
From: Tilman Schmidt <tilman-ZTO5kqT2PaM@public.gmane.org>
Date: Wed, 7 Oct 2009 00:18:21 +0200 (CEST)
> This is the third release of the series of patches for the Gigaset
> drivers I first submitted on 2009-09-06. I have dropped the first patch
> "gigaset: really fix chars_in_buffer" because it has now been merged
> through the tty tree, and folded into the last one the fixes I posted on
> 2009-09-25 and 2009-10-01. Apart from that, the series is unchanged from
> the second submission on 2009-09-19. It would be great if this could
> still make it into release 2.6.32 as one more step on the way to get rid
> of the deprecated ISDN4Linux subsystem.
I applied patches 1-8 to net-2.6, merged net-2.6 into net-next-2.6,
then added patches 9-11 into net-next-2.6
Thanks!
next prev parent reply other threads:[~2009-10-07 6:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 22:18 [PATCH 00/11] Gigaset driver patches for 2.6.32 (v3) Tilman Schmidt
2009-10-06 22:18 ` [PATCH 01/11] gigaset: fix reject/hangup handling Tilman Schmidt
2009-10-06 22:18 ` [PATCH 02/11] gigaset: linearize skb Tilman Schmidt
2009-10-06 22:18 ` [PATCH 03/11] gigaset: handle isoc frame errors more gracefully Tilman Schmidt
2009-10-06 22:18 ` [PATCH 04/11] gigaset: announce if built with debugging Tilman Schmidt
2009-10-06 22:18 ` [PATCH 05/11] gigaset: fix device ERROR response handling Tilman Schmidt
2009-10-06 22:19 ` [PATCH 08/11] gigaset: add kerneldoc comments Tilman Schmidt
[not found] ` <20091006-patch-gigaset-00.tilman-ZTO5kqT2PaM@public.gmane.org>
2009-10-06 22:18 ` [PATCH 06/11] gigaset: improve error recovery Tilman Schmidt
2009-10-06 22:18 ` [PATCH 07/11] gigaset: correct debugging output selection Tilman Schmidt
2009-10-06 22:19 ` [PATCH 09/11] gigaset: prepare for CAPI implementation Tilman Schmidt
2009-10-06 22:19 ` [PATCH 11/11] gigaset: add Kernel CAPI interface (v3) Tilman Schmidt
2009-10-07 6:39 ` David Miller [this message]
[not found] ` <1254904188.9411@nb-hp>
2009-10-07 8:30 ` [PATCH 00/11] Gigaset driver patches for 2.6.32 (v3) David Miller
2009-10-06 22:19 ` [PATCH 10/11] gigaset: allow building without I4L Tilman Schmidt
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=20091006.233901.192206610.davem@davemloft.net \
--to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
--cc=hjlipp-S0/GAf8tV78@public.gmane.org \
--cc=i4ldeveloper-JX7+OpRa80SjiSfgN6Y1Ib39b6g2fGNp@public.gmane.org \
--cc=isdn-iHCpqvpFUx0uJkBD2foKsQ@public.gmane.org \
--cc=isdn4linux-JX7+OpRa80SjiSfgN6Y1Ib39b6g2fGNp@public.gmane.org \
--cc=keil-shG/GajIFYqbacvFa/9K2g@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tilman-ZTO5kqT2PaM@public.gmane.org \
/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).