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 1/2] staging: comedi: addi_apci_1564: board does not have analog inputs
Date: Fri, 25 Apr 2014 11:18:38 +0100 [thread overview]
Message-ID: <535A367E.7020105@mev.co.uk> (raw)
In-Reply-To: <1398413826-19400-1-git-send-email-chase.southwood@gmail.com>
On 2014-04-25 09:17, Chase Southwood wrote:
> This board does not have analog inputs. Remove the subdevice init for
> them.
>
> Signed-off-by: Chase Southwood <chase.southwood@gmail.com>
> Cc: Ian Abbott <abbotti@mev.co.uk>
> Cc: H Hartley Sweeten <hsweeten@visionengravers.com>
> ---
> Compile tested only. To be applied on top of
> [PATCH] staging: comedi: addi_apci_1564: separate from addi_common.c
Looks good. May want to get rid of the unused subdevices at some point
during the cleanup.
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 )=-
next prev parent reply other threads:[~2014-04-25 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 8:17 [PATCH 1/2] staging: comedi: addi_apci_1564: board does not have analog inputs Chase Southwood
2014-04-25 8:18 ` [PATCH 2/2] staging: comedi: addi_apci_1564: board does not have analog outputs Chase Southwood
2014-04-25 10:20 ` Ian Abbott
2014-04-25 16:08 ` Hartley Sweeten
2014-04-25 10:18 ` Ian Abbott [this message]
2014-04-25 16:07 ` [PATCH 1/2] staging: comedi: addi_apci_1564: board does not have analog inputs Hartley Sweeten
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=535A367E.7020105@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