From: Jonathan Cameron <jic23@cam.ac.uk>
To: michael.hennerich@analog.com
Cc: greg@kroah.com, linux-iio@vger.kernel.org, drivers@analog.com,
device-drivers-devel@blackfin.uclinux.org,
randy.dunlap@oracle.com, devel@driverdev.osuosl.org,
sfr@canb.auug.org.au, linux-next@vger.kernel.org
Subject: Re: [PATCH] staging: iio: ad7476: fix !CONFIG_IIO_RING_BUFFER build issue reported by Randy Dunlap
Date: Thu, 14 Oct 2010 11:22:48 +0100 [thread overview]
Message-ID: <4CB6D9F8.9090107@cam.ac.uk> (raw)
In-Reply-To: <1287044238-20220-1-git-send-email-michael.hennerich@analog.com>
On 10/14/10 09:17, michael.hennerich@analog.com wrote:
> From: Michael Hennerich <michael.hennerich@analog.com>
>
> Fix function function decalration
> Enable CONFIG_IIO_RING_BUFFER for the ad7476 driver
>
> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
> ---
> drivers/staging/iio/adc/Kconfig | 3 +++
> drivers/staging/iio/adc/ad7476.h | 4 +---
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/iio/adc/Kconfig b/drivers/staging/iio/adc/Kconfig
> index 81a7d45..acb6767 100644
> --- a/drivers/staging/iio/adc/Kconfig
> +++ b/drivers/staging/iio/adc/Kconfig
> @@ -50,6 +50,9 @@ config AD799X_RING_BUFFER
> config AD7476
> tristate "Analog Devices AD7475/6/7/8 AD7466/7/8 and AD7495 ADC driver"
> depends on SPI
> + select IIO_RING_BUFFER
> + select IIO_SW_RING
> + select IIO_TRIGGER
> help
> Say yes here to build support for Analog Devices
> AD7475, AD7476, AD7477, AD7478, AD7466, AD7467, AD7468, AD7495
> diff --git a/drivers/staging/iio/adc/ad7476.h b/drivers/staging/iio/adc/ad7476.h
> index 6e4a85b..b51b49e 100644
> --- a/drivers/staging/iio/adc/ad7476.h
> +++ b/drivers/staging/iio/adc/ad7476.h
> @@ -59,9 +59,7 @@ int ad7476_scan_from_ring(struct ad7476_state *st);
> int ad7476_register_ring_funcs_and_init(struct iio_dev *indio_dev);
> void ad7476_ring_cleanup(struct iio_dev *indio_dev);
> #else /* CONFIG_IIO_RING_BUFFER */
If you are selecting the ring buffer (which is fine), then why do you need
anything to be in this else? The buffer will always be there.
Maybe I'm missing something?
> -static inline ssize_t ad7476_scan_from_ring(struct device *dev,
> - struct device_attribute *attr,
> - char *buf)
> +static inline int ad7476_scan_from_ring(struct ad7476_state *st)
> {
> return 0;
> }
next prev parent reply other threads:[~2010-10-14 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 8:17 [PATCH] staging: iio: ad7476: fix !CONFIG_IIO_RING_BUFFER build issue reported by Randy Dunlap michael.hennerich
2010-10-14 10:22 ` Jonathan Cameron [this message]
2010-10-14 11:06 ` Hennerich, Michael
2010-10-14 11:20 ` Jonathan Cameron
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=4CB6D9F8.9090107@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=devel@driverdev.osuosl.org \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=drivers@analog.com \
--cc=greg@kroah.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).