From: Jonathan Cameron <jic23@kernel.org>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, knaack.h@gmx.de,
pmeerw@pmeerw.net, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-usp@googlegroups.com
Subject: Re: [PATCH v4 4/7] staging: iio: ad5933: change help rule message
Date: Sat, 16 Mar 2019 18:38:34 +0000 [thread overview]
Message-ID: <20190316183834.0e6ae2e4@archlinux> (raw)
In-Reply-To: <20190316150718.kl27r5vqendxj3mw@smtp.gmail.com>
On Sat, 16 Mar 2019 12:07:18 -0300
Marcelo Schmitt <marcelo.schmitt1@gmail.com> wrote:
> Remove the previous comment about direct access via sysfs which would
> lead one think ad5933 driver has limitations it actually doesn't.
>
> Signed-off-by: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Applied.
Thanks,
Jonathan
> ---
> drivers/staging/iio/impedance-analyzer/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/impedance-analyzer/Kconfig b/drivers/staging/iio/impedance-analyzer/Kconfig
> index dd97b6bb3fd0..b9a679cdd146 100644
> --- a/drivers/staging/iio/impedance-analyzer/Kconfig
> +++ b/drivers/staging/iio/impedance-analyzer/Kconfig
> @@ -10,7 +10,7 @@ config AD5933
> select IIO_KFIFO_BUF
> help
> Say yes here to build support for Analog Devices Impedance Converter,
> - Network Analyzer, AD5933/4, provides direct access via sysfs.
> + Network Analyzer, AD5933/4.
>
> To compile this driver as a module, choose M here: the
> module will be called ad5933.
prev parent reply other threads:[~2019-03-16 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 15:07 [PATCH v4 4/7] staging: iio: ad5933: change help rule message Marcelo Schmitt
2019-03-16 18:38 ` 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=20190316183834.0e6ae2e4@archlinux \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=kernel-usp@googlegroups.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=pmeerw@pmeerw.net \
/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).