From: Jonathan Cameron <jic23@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com,
stefan.popa@analog.com, knaack.h@gmx.de, pmeerw@pmeerw.net,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] iio: dac: ad5592r: Fix a typo in the name of a function
Date: Sat, 25 Apr 2020 17:55:57 +0100 [thread overview]
Message-ID: <20200425175557.20cd9256@archlinux> (raw)
In-Reply-To: <20200425070056.31664-1-christophe.jaillet@wanadoo.fr>
On Sat, 25 Apr 2020 09:00:56 +0200
Christophe JAILLET <christophe.jaillet@wanadoo.fr> wrote:
> This module is related to AD5592R, not AD5593R, so be consistent in naming.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Applied
Thanks,
Jonathan
> ---
> drivers/iio/dac/ad5592r.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/dac/ad5592r.c b/drivers/iio/dac/ad5592r.c
> index 34ba059a77da..49308ad13c4b 100644
> --- a/drivers/iio/dac/ad5592r.c
> +++ b/drivers/iio/dac/ad5592r.c
> @@ -98,7 +98,7 @@ static int ad5592r_reg_read(struct ad5592r_state *st, u8 reg, u16 *value)
> return 0;
> }
>
> -static int ad5593r_gpio_read(struct ad5592r_state *st, u8 *value)
> +static int ad5592r_gpio_read(struct ad5592r_state *st, u8 *value)
> {
> int ret;
>
> @@ -121,7 +121,7 @@ static const struct ad5592r_rw_ops ad5592r_rw_ops = {
> .read_adc = ad5592r_read_adc,
> .reg_write = ad5592r_reg_write,
> .reg_read = ad5592r_reg_read,
> - .gpio_read = ad5593r_gpio_read,
> + .gpio_read = ad5592r_gpio_read,
> };
>
> static int ad5592r_spi_probe(struct spi_device *spi)
prev parent reply other threads:[~2020-04-25 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 7:00 [PATCH] iio: dac: ad5592r: Fix a typo in the name of a function Christophe JAILLET
2020-04-25 16:55 ` 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=20200425175557.20cd9256@archlinux \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=stefan.popa@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