From: Ian Abbott <abbotti@mev.co.uk>
To: Chase Southwood <chase.southwood@gmail.com>,
<gregkh@linuxfoundation.org>
Cc: <hsweeten@visionengravers.com>, <devel@driverdev.osuosl.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] staging: comedi: addi_apci_1564: miscellaneous cleanups
Date: Tue, 12 Aug 2014 10:29:01 +0100 [thread overview]
Message-ID: <53E9DE5D.3010403@mev.co.uk> (raw)
In-Reply-To: <cover.1407804777.git.chase.southwood@gmail.com>
On 2014-08-12 03:02, Chase Southwood wrote:
> This patchset removes an uncorrect and unneeded insn_config operation,
> strips out remaining in-driver watchdog subdevice code, and cleans up the
> driver's register map defines.
>
> Chase Southwood (3):
> staging: comedi: addi_apci_1564: remove apci1564_do_config
> staging: comedi: addi_apci_1564: Remove in-driver watchdog support
> code
> staging: comedi: addi_apci_1564: tidy register map defines
>
> .../comedi/drivers/addi-data/hwdrv_apci1564.c | 158 +++++++--------------
> drivers/staging/comedi/drivers/addi_apci_1564.c | 20 +--
> 2 files changed, 60 insertions(+), 118 deletions(-)
>
Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
prev parent reply other threads:[~2014-08-12 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 2:02 [PATCH 0/3] staging: comedi: addi_apci_1564: miscellaneous cleanups Chase Southwood
2014-08-12 2:02 ` [PATCH 1/3] staging: comedi: addi_apci_1564: remove apci1564_do_config Chase Southwood
2014-08-12 2:03 ` [PATCH 2/3] staging: comedi: addi_apci_1564: Remove in-driver watchdog support code Chase Southwood
2014-08-12 2:03 ` [PATCH 3/3] staging: comedi: addi_apci_1564: tidy register map defines Chase Southwood
2014-08-12 9:29 ` Ian Abbott [this message]
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=53E9DE5D.3010403@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=chase.southwood@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.