From: Tilman Schmidt <tilman@imap.cc>
To: Karsten Keil <isdn@linux-pingi.de>, Karsten Keil <keil@b1-systems.de>
Cc: davem@davemloft.net, i4ldeveloper@listserv.isdn4linux.de,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] ISDN patches for 2.6.32 (v2)
Date: Sat, 26 Sep 2009 13:44:31 +0200 [thread overview]
Message-ID: <4ABDFE9F.2030404@imap.cc> (raw)
In-Reply-To: <20090919-patch-capi-0.tilman@imap.cc>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
Hello Karsten,
is there any chance of getting these and the Gigaset patches forwarded
for inclusion in 2.6.32 before the merge window closes?
If not all of them, perhaps at least those which you had already acked
before David Miller asked that they should formally go through you
(#2-4 of the ISDN series), and those which are just fixes to the
existing i4l version of the driver (#1-10 of the Gigaset series)?
I would really appreciate not having to maintain all of them out of
tree for another release cycle.
Thanks a lot,
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2009-09-26 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 23:57 [PATCH 0/4] ISDN patches for 2.6.32 (v2) Tilman Schmidt
2009-09-18 23:57 ` [PATCH 2/4] isdn: accept CAPI Informational Info values as success Tilman Schmidt
2009-09-18 23:57 ` [PATCH 1/4] Documentation: expand isdn/INTERFACE.CAPI document Tilman Schmidt
2009-09-18 23:57 ` [PATCH 3/4] isdn: avoid races in capidrv (v2) Tilman Schmidt
2009-09-18 23:57 ` [PATCH 4/4] isdn: make capidrv module parameter "debugmode" writeable Tilman Schmidt
2009-09-26 11:44 ` Tilman Schmidt [this message]
2009-09-27 3:24 ` [PATCH 0/4] ISDN patches for 2.6.32 (v2) 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=4ABDFE9F.2030404@imap.cc \
--to=tilman@imap.cc \
--cc=davem@davemloft.net \
--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 \
/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).