From: Tilman Schmidt <tilman@imap.cc>
To: davem@davemloft.net, Karsten Keil <keil@b1-systems.de>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
i4ldeveloper@listserv.isdn4linux.de
Subject: [PATCH 0/4] ISDN patches for 2.6.32
Date: Sun, 6 Sep 2009 20:58:52 +0200 (CEST) [thread overview]
Message-ID: <20090906-patch-capi-0.tilman@imap.cc> (raw)
Dave,
following are four patches for the Kernel CAPI ISDN subsystem which arose as
by-products of my work on the Gigaset driver: one documentation update, two
bugfixes (acked by the ISDN maintainer), and a debugging aid. Would you please
take them into your net tree for merging in kernel release 2.6.32.
Thanks,
Tilman
next reply other threads:[~2009-09-06 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 18:58 Tilman Schmidt [this message]
2009-09-06 18:58 ` [PATCH 4/4] isdn: make capidrv module parameter "debugmode" writeable Tilman Schmidt
[not found] ` <20090906-patch-capi-0.tilman-ZTO5kqT2PaM@public.gmane.org>
2009-09-06 18:58 ` [PATCH 2/4] isdn: accept CAPI Informational Info values as success Tilman Schmidt
2009-09-06 18:58 ` [PATCH 1/4] Documentation: expand isdn/INTERFACE.CAPI document Tilman Schmidt
2009-09-06 18:58 ` [PATCH 3/4] isdn: avoid races in capidrv 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=20090906-patch-capi-0.tilman@imap.cc \
--to=tilman@imap.cc \
--cc=davem@davemloft.net \
--cc=i4ldeveloper@listserv.isdn4linux.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).