From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 1/2] iio:health:afe4403: Fix naming of tx supply to match dt-bindings
Date: Sun, 21 Feb 2021 16:27:13 +0000 [thread overview]
Message-ID: <20210221162713.35634481@archlinux> (raw)
In-Reply-To: <20201128162334.382837-1-jic23@kernel.org>
On Sat, 28 Nov 2020 16:23:33 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> These have always been different and the name tx_sup-supply that
> would work for the driver is rather nonsensical so let us go with
> what was described in the dt-binding doc.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Fixes: eec96d1e2d318 ("iio: health: Add driver for the TI AFE4403 heart monitor")
Another old series that I could do with a sanity check / review on.
Thanks,
Jonathan
> ---
> drivers/iio/health/afe4403.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/health/afe4403.c b/drivers/iio/health/afe4403.c
> index 38734e4ce360..94bbfc065bed 100644
> --- a/drivers/iio/health/afe4403.c
> +++ b/drivers/iio/health/afe4403.c
> @@ -486,7 +486,7 @@ static int afe4403_probe(struct spi_device *spi)
> }
> }
>
> - afe->regulator = devm_regulator_get(afe->dev, "tx_sup");
> + afe->regulator = devm_regulator_get(afe->dev, "tx");
> if (IS_ERR(afe->regulator)) {
> dev_err(afe->dev, "Unable to get regulator\n");
> return PTR_ERR(afe->regulator);
prev parent reply other threads:[~2021-02-21 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 16:23 [PATCH 1/2] iio:health:afe4403: Fix naming of tx supply to match dt-bindings Jonathan Cameron
2020-11-28 16:23 ` [PATCH 2/2] iio:health:afe4404: " Jonathan Cameron
2021-02-21 16:27 ` 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=20210221162713.35634481@archlinux \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=linux-iio@vger.kernel.org \
/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