From: Tilman Schmidt <tilman@imap.cc>
To: i4ldeveloper@listserv.isdn4linux.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Hansjoerg Lipp <hjlipp@web.de>
Subject: [PATCH RFC 0/6] Gigaset driver port to CAPI
Date: Fri, 21 Aug 2009 19:21:34 +0200 (CEST) [thread overview]
Message-ID: <20090821-patch-00.tilman@imap.cc> (raw)
Folks,
the following set of six patches adds a configuration option to the
Gigaset driver to interface to Kernel CAPI instead of the old
ISDN4Linux subsystem. Although my unit test are not quite done yet
I would appreciate comments.
The patchset is based on 2.6.31-rc6. The first two patches are
bugfixes to the existing driver, the third one adds kerneldoc
comments for a few functions. These three are included just so
that the following ones will apply cleanly, although you are
welcome to comment on them, too.
Patch 4 reorganizes the existing driver's code so that the new
interface can be fitted in.
Patch 5 adds the Kconfig mechanism for making the ISDN subsystem
interface selectable.
Patch 6 finally adds the actual Kernel CAPI interface, and is of
course the one I am most eager to hear opinions about.
Thanks,
Tilman
next reply other threads:[~2009-08-21 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 17:21 Tilman Schmidt [this message]
2009-08-21 17:21 ` [PATCH RFC 4/6] gigaset: prepare for CAPI implementation Tilman Schmidt
2009-08-21 17:21 ` [PATCH RFC 6/6] gigaset: add Kernel CAPI interface Tilman Schmidt
2009-08-21 17:21 ` [PATCH RFC 3/6] gigaset: add kerneldoc comments Tilman Schmidt
2009-08-21 17:21 ` [PATCH RFC 5/6] gigaset: allow building without I4L Tilman Schmidt
2009-08-21 17:21 ` [PATCH RFC 1/6] gigaset: fix reject/hangup handling Tilman Schmidt
2009-08-21 17:21 ` [PATCH RFC 2/6] gigaset: handle isoc frame errors more gracefully Tilman Schmidt
2009-08-24 23:58 ` [PATCH RFC 0/6] Gigaset driver port to CAPI 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=20090821-patch-00.tilman@imap.cc \
--to=tilman@imap.cc \
--cc=hjlipp@web.de \
--cc=i4ldeveloper@listserv.isdn4linux.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).