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] staging: iio: dds: ad9832: Fix kconfig description
Date: Wed, 01 Dec 2010 16:46:07 +0000 [thread overview]
Message-ID: <4CF67BCF.7010102@cam.ac.uk> (raw)
In-Reply-To: <1291220542-24848-1-git-send-email-michael.hennerich@analog.com>
On 12/01/10 16:22, michael.hennerich@analog.com wrote:
> From: Michael Hennerich <michael.hennerich@analog.com>
>
> The AD9832 driver doesn't support the AD9833 and AD9834
>
For what it's worth...
> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
Acked-by: Jonathan Cameron <jic23@cam.ac.uk>
> ---
> drivers/staging/iio/dds/Kconfig | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/iio/dds/Kconfig b/drivers/staging/iio/dds/Kconfig
> index d045ed6..7969be2 100644
> --- a/drivers/staging/iio/dds/Kconfig
> +++ b/drivers/staging/iio/dds/Kconfig
> @@ -11,11 +11,11 @@ config AD5930
> ad5930/ad5932, provides direct access via sysfs.
>
> config AD9832
> - tristate "Analog Devices ad9832/3/4/5 driver"
> + tristate "Analog Devices ad9832/5 driver"
> depends on SPI
> help
> Say yes here to build support for Analog Devices DDS chip
> - ad9832/3/4/5, provides direct access via sysfs.
> + ad9832 and ad9835, provides direct access via sysfs.
>
> config AD9850
> tristate "Analog Devices ad9850/1 driver"
next prev parent reply other threads:[~2010-12-01 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 16:22 [PATCH] staging: iio: dds: ad9832: Fix kconfig description michael.hennerich
2010-12-01 16:46 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-01 16:34 michael.hennerich
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=4CF67BCF.7010102@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 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.