From: H Hartley Sweeten <hartleys@visionengravers.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: <devel@driverdev.osuosl.org>, <abbotti@mev.co.uk>,
<fmhess@users.sourceforge.net>, <gregkh@linuxfoundation.org>
Subject: [PATCH 00/12] staging: comedi: s626: start cleaning up the driver
Date: Wed, 20 Jun 2012 19:22:57 -0700 [thread overview]
Message-ID: <201206201922.58120.hartleys@visionengravers.com> (raw)
The s626 driver is a bit of a mess...
Start cleaning it up by getting rid of some sparse warnings, all the
forward declarations, the DEBUG function tracing, an unused
macro, and factoring out the PCI device matching code.
H Hartley Sweeten (12):
staging: comedi: s626: local functions should not be exposed globally
staging: comedi: s626: pointers should be cleared with NULL not 0
staging: comedi: s626: remove forward declarations 1
staging: comedi: s626: remove forward declarations 2
staging: comedi: s626: remove forward declarations 3
staging: comedi: s626: remove forward declarations 4
staging: comedi: s626: remove forward declarations 5
staging: comedi: s626: remove forward declarations 6
staging: comedi: s626: remove forward declarations 7
staging: comedi: s626: remove private DEBUG macro
staging: comedi: s626: remove private INLINE macro
staging: comedi: s626: factor out the find PCI device code
drivers/staging/comedi/drivers/s626.c | 3075 +++++++++++++++------------------
drivers/staging/comedi/drivers/s626.h | 10 -
2 files changed, 1377 insertions(+), 1708 deletions(-)
--
1.7.11
reply other threads:[~2012-06-21 2:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201206201922.58120.hartleys@visionengravers.com \
--to=hartleys@visionengravers.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®