From: Sean Young <sean@mess.org>
To: wuxilin123@gmail.com
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH] media: rc: ir-spi: Correct regulator name
Date: Fri, 11 Aug 2023 10:57:18 +0100 [thread overview]
Message-ID: <ZNYF/iGqrBQrV3IT@gofer.mess.org> (raw)
In-Reply-To: <20230805-ir-spi-v1-1-33af4a556139@gmail.com>
On Sat, Aug 05, 2023 at 07:23:35PM +0800, Xilin Wu via B4 Relay wrote:
> From: Xilin Wu <wuxilin123@gmail.com>
>
> The driver wrongly assumes regulator is called "irda_regulator"
> instead of "power".
>
> Change it to "power" to match device tree binding.
>
> Signed-off-by: Xilin Wu <wuxilin123@gmail.com>
> ---
> drivers/media/rc/ir-spi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/rc/ir-spi.c b/drivers/media/rc/ir-spi.c
> index bbc81bed4f90..a447bb36100d 100644
> --- a/drivers/media/rc/ir-spi.c
> +++ b/drivers/media/rc/ir-spi.c
> @@ -119,7 +119,7 @@ static int ir_spi_probe(struct spi_device *spi)
> if (!idata)
> return -ENOMEM;
>
> - idata->regulator = devm_regulator_get(&spi->dev, "irda_regulator");
> + idata->regulator = devm_regulator_get(&spi->dev, "power");
I agree that irda_regulator is not a great name and it probably should have
been picked up in review. However, is it safe to change without breaking
backwards compatibility?
Rob, what do you think?
Thanks
Sean
> if (IS_ERR(idata->regulator))
> return PTR_ERR(idata->regulator);
>
>
> ---
> base-commit: 024ff300db33968c133435a146d51ac22db27374
> change-id: 20230805-ir-spi-3473c5f34764
>
> Best regards,
> --
> Xilin Wu <wuxilin123@gmail.com>
prev parent reply other threads:[~2023-08-11 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 11:23 Xilin Wu via B4 Relay
2023-08-11 9:57 ` Sean Young [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=ZNYF/iGqrBQrV3IT@gofer.mess.org \
--to=sean@mess.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=wuxilin123@gmail.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
all inboxes | Powered by JetHome®