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/2] staging: comedi: addi_apci_1564: provide interface to read diagnostic status
Date: Fri, 1 Aug 2014 13:26:17 +0100 [thread overview]
Message-ID: <53DB8769.2020409@mev.co.uk> (raw)
In-Reply-To: <cover.1406857380.git.chase.southwood@gmail.com>
On 01/08/14 02:55, Chase Southwood wrote:
> This patchset creates a simple subdevice to allow for reading of the
> board's diagnostic status, and then removes any code which is related to
> diagnostic interrupts, as the driver will not support these at this time.
>
> Chase Southwood (2):
> staging: comedi: addi_apci_1564: add subdevice to check diagnostic
> status
> staging: comedi: addi_apci_1564: remove diagnostic interrupt support
> code
>
> .../comedi/drivers/addi-data/hwdrv_apci1564.c | 14 --------
> drivers/staging/comedi/drivers/addi_apci_1564.c | 41 ++++++++++++----------
> 2 files changed, 22 insertions(+), 33 deletions(-)
>
The Digital Output subdevice should behave more sanely now!
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-01 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 1:55 [PATCH 0/2] staging: comedi: addi_apci_1564: provide interface to read diagnostic status Chase Southwood
2014-08-01 1:56 ` [PATCH 1/2] staging: comedi: addi_apci_1564: add subdevice to check " Chase Southwood
2014-08-01 1:56 ` [PATCH 2/2] staging: comedi: addi_apci_1564: remove diagnostic interrupt support code Chase Southwood
2014-08-01 12:26 ` 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=53DB8769.2020409@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox