From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Claudiu Beznea <claudiu.beznea@microchip.com>
Cc: <srinivas.kandagatla@linaro.org>, <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvmem: lan9662-otp: fix compatible name
Date: Wed, 26 Oct 2022 01:44:05 +0200 [thread overview]
Message-ID: <20221025234405.wr3copoyi4mj472t@soft-dev3-1> (raw)
In-Reply-To: <20221025072217.3715634-1-claudiu.beznea@microchip.com>
The 10/25/2022 10:22, Claudiu Beznea wrote:
Hi Claudiu,
> Documentation of lan9662-otpc driver (namely Documentation/\
> devicetree/bindings/nvmem/microchip,lan9662-otpc.yaml) express that
> compatible for this driver contains "otpc" string at the end but not "otp"
> as currently present. Fix this typo.
Thanks for this patch.
I have also sent a patch for this some time ago[1], but there
is no reply on this.
Anyway for this patch:
Reviewed-by: Horatiu Vultur <horatiu.vultur@microchip.com>
[1] https://patchew.org/linux/20220928195112.630351-1-horatiu.vultur@microchip.com/
>
> Fixes: 9e8f208ad522 ("nvmem: lan9662-otp: add support")
> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> ---
> drivers/nvmem/lan9662-otpc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/nvmem/lan9662-otpc.c b/drivers/nvmem/lan9662-otpc.c
> index f6732fd216d8..377bf34c2946 100644
> --- a/drivers/nvmem/lan9662-otpc.c
> +++ b/drivers/nvmem/lan9662-otpc.c
> @@ -203,7 +203,7 @@ static int lan9662_otp_probe(struct platform_device *pdev)
> }
>
> static const struct of_device_id lan9662_otp_match[] = {
> - { .compatible = "microchip,lan9662-otp", },
> + { .compatible = "microchip,lan9662-otpc", },
> { },
> };
> MODULE_DEVICE_TABLE(of, lan9662_otp_match);
> --
> 2.34.1
>
--
/Horatiu
next prev parent reply other threads:[~2022-10-25 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 7:22 [PATCH] nvmem: lan9662-otp: fix compatible name Claudiu Beznea
2022-10-25 23:44 ` Horatiu Vultur [this message]
2022-11-10 17:45 ` Greg KH
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=20221025234405.wr3copoyi4mj472t@soft-dev3-1 \
--to=horatiu.vultur@microchip.com \
--cc=claudiu.beznea@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.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;
as well as URLs for NNTP newsgroup(s).