From: Chase Southwood <chase.southwood@gmail.com>
To: gregkh@linuxfoundation.org
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Chase Southwood <chase.southwood@gmail.com>
Subject: [PATCH 0/4] staging: comedi: addi_apci_1564: small fixes in apci1564_auto_attach() and apci1564_detach()
Date: Thu, 10 Jul 2014 23:00:54 -0500 [thread overview]
Message-ID: <cover.1405050794.git.chase.southwood@gmail.com> (raw)
This is a small patchset containing a handful of fixes to the ADDI-DATA
APCI1564 driver that I would like to get out of the way before I forget
to take care of them. From here, I will move to start fixing the
digital input/timer/counters/watchdog functionality of the board.
Chase Southwood (4):
staging: comedi: addi_apci_1564: remove len_chanlist from di and do
subdevices
staging: comedi: addi_apci_1564: remove unnecessary dev->board_name
initialization
staging: comedi: addi_apci_1564: remove null check of devpriv in
apci1564_detach()
staging: comedi: addi_apci_1564: fix s->maxdata assignment in do
subdevice init.
drivers/staging/comedi/drivers/addi_apci_1564.c | 18 +++++-------------
1 file changed, 5 insertions(+), 13 deletions(-)
--
2.0.1
next reply other threads:[~2014-07-11 4:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 4:00 Chase Southwood [this message]
2014-07-11 4:01 ` [PATCH 1/4] staging: comedi: addi_apci_1564: remove len_chanlist from di and do subdevices Chase Southwood
2014-07-11 4:02 ` [PATCH 2/4] staging: comedi: addi_apci_1564: remove unnecessary dev->board_name initialization Chase Southwood
2014-07-11 4:02 ` [PATCH 3/4] staging: comedi: addi_apci_1564: remove null check of devpriv in apci1564_detach() Chase Southwood
2014-07-11 4:02 ` [PATCH 4/4] staging: comedi: addi_apci_1564: fix s->maxdata assignment in do subdevice init Chase Southwood
2014-07-11 10:24 ` [PATCH 0/4] staging: comedi: addi_apci_1564: small fixes in apci1564_auto_attach() and apci1564_detach() Ian Abbott
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=cover.1405050794.git.chase.southwood@gmail.com \
--to=chase.southwood@gmail.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--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