From: Tilman Schmidt <tilman@imap•cc>
To: David Miller <davem@davemloft•net>,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org
Cc: Karsten Keil <isdn@linux-pingi•de>,
Karsten Keil <keil@b1-systems•de>,
isdn4linux@listserv•isdn4linux.de,
i4ldeveloper@listserv•isdn4linux.de
Subject: [PATCH 0/4] ISDN patches for 2.6.32 (v3)
Date: Wed, 7 Oct 2009 00:17:55 +0200 (CEST) [thread overview]
Message-ID: <20091006-patch-capi-0.tilman@imap.cc> (raw)
David,
as I still haven't heard anything from Karsten and none of the other
ISDN developers has volunteered to step into the breach, I would like to
get back to the suggestion of merging my ISDN patches through you.
Here is a respin of the four patches for the Kernel CAPI subsystem I
first submitted on 2009-09-06. I have folded into patch 1 the amendment
I posted as "patch 5/4" on 2009-09-25, and re-added to patches 2 and 3
Karsten's original Acked-by that came out of the discussion on the
isdn4linux mailing list. Apart from that, the series is unchanged from
the second submission on 2009-09-19.
I'll be following up with the respun patches to the Gigaset driver.
It would be great if these could still be integrated into kernel release
2.6.32.
Thanks,
Tilman
next reply other threads:[~2009-10-06 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 22:17 Tilman Schmidt [this message]
[not found] ` <20091006-patch-capi-0.tilman-ZTO5kqT2PaM@public.gmane.org>
2009-10-06 22:18 ` [PATCH 1/4] Documentation: expand isdn/INTERFACE.CAPI document Tilman Schmidt
2009-10-06 22:18 ` [PATCH 2/4] isdn: accept CAPI Informational Info values as success Tilman Schmidt
2009-10-06 22:18 ` [PATCH 3/4] isdn: avoid races in capidrv Tilman Schmidt
2009-10-06 22:18 ` [PATCH 4/4] isdn: make capidrv module parameter "debugmode" writeable Tilman Schmidt
2009-10-07 0:36 ` [PATCH 0/4] ISDN patches for 2.6.32 (v3) David Miller
2009-10-07 6:38 ` 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=20091006-patch-capi-0.tilman@imap.cc \
--to=tilman@imap$(echo .)cc \
--cc=davem@davemloft$(echo .)net \
--cc=i4ldeveloper@listserv$(echo .)isdn4linux.de \
--cc=isdn4linux@listserv$(echo .)isdn4linux.de \
--cc=isdn@linux-pingi$(echo .)de \
--cc=keil@b1-systems$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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