Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: michael.hennerich@analog.com
Cc: linux-iio@vger.kernel.org, drivers@analog.com,
	device-drivers-devel@blackfin.uclinux.org
Subject: Re: [PATCH 1/2] IIO-onwards: ADC: AD7887: Convert to new channel registration method.
Date: Mon, 18 Apr 2011 14:36:56 +0100	[thread overview]
Message-ID: <4DAC3E78.4060001@cam.ac.uk> (raw)
In-Reply-To: <1303131831-4010-1-git-send-email-michael.hennerich@analog.com>

On 04/18/11 14:03, michael.hennerich@analog.com wrote:
> From: Michael Hennerich <michael.hennerich@analog.com>
> 
> Convert to new channel registration method
> Update / change license copyright header
> Add missing call to iio_trigger_notify_done()
Looks good.  I wonder if it would make more sense to have the channel
definitions external to the chip_info structure (have a pointer and size
parameter in there.)  That would allow the driver to handle devices with
different numbers of channels.  Right now it's irrelevant though and can
be easily enough fixed when/if it becomes an issue.

Thanks,

Will slot this one into relevant spot in iio-onwards.
> 
> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
Acked-by: Jonathan Cameron <jic23@cam.ac.uk>
> ---
>  drivers/staging/iio/adc/ad7887.h      |   14 ++--
>  drivers/staging/iio/adc/ad7887_core.c |  123 ++++++++++++++-------------------
>  drivers/staging/iio/adc/ad7887_ring.c |   71 +++-----------------
>  3 files changed, 69 insertions(+), 139 deletions(-)

      parent reply	other threads:[~2011-04-18 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18 13:03 [PATCH 1/2] IIO-onwards: ADC: AD7887: Convert to new channel registration method michael.hennerich
2011-04-18 13:03 ` [PATCH 2/2] IIO-onwards: ADC: AD7887: Use private data space from iio_allocate_device michael.hennerich
2011-04-18 13:38   ` Jonathan Cameron
2011-04-18 13:36 ` Jonathan Cameron [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=4DAC3E78.4060001@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=drivers@analog.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    /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