From: Srinivas Kandagatla <srini@kernel.org>
To: Cosmin Tanislav <cosmin-gabriel.tanislav.xa@renesas.com>
Cc: Srinivas Kandagatla <srini@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmem: rcar-efuse: add missing MODULE_DEVICE_TABLE
Date: Thu, 11 Sep 2025 09:57:15 +0100 [thread overview]
Message-ID: <6018d919-be3f-4f12-a7e1-3128b895cad7@kernel.org> (raw)
In-Reply-To: <20250910175415.8698-1-cosmin-gabriel.tanislav.xa@renesas.com>
On 9/10/25 6:54 PM, Cosmin Tanislav wrote:
> The nvmem-rcar-efuse driver can be compiled as a module. Add missing
> MODULE_DEVICE_TABLE so it can be matched by modalias and automatically
> loaded by udev.
>
> Fixes: 1530b923a514 ("nvmem: Add R-Car E-FUSE driver")
Missing Stable tag.
--srini
> Signed-off-by: Cosmin Tanislav <cosmin-gabriel.tanislav.xa@renesas.com>
> ---
> drivers/nvmem/rcar-efuse.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/nvmem/rcar-efuse.c b/drivers/nvmem/rcar-efuse.c
> index f24bdb9cb5a7..d9a96a1d59c8 100644
> --- a/drivers/nvmem/rcar-efuse.c
> +++ b/drivers/nvmem/rcar-efuse.c
> @@ -127,6 +127,7 @@ static const struct of_device_id rcar_fuse_match[] = {
> { .compatible = "renesas,r8a779h0-otp", .data = &rcar_fuse_v4m },
> { /* sentinel */ }
> };
> +MODULE_DEVICE_TABLE(of, rcar_fuse_match);
>
> static struct platform_driver rcar_fuse_driver = {
> .probe = rcar_fuse_probe,
prev parent reply other threads:[~2025-09-11 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 17:54 Cosmin Tanislav
2025-09-11 8:01 ` Geert Uytterhoeven
2025-09-11 8:57 ` Srinivas Kandagatla [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=6018d919-be3f-4f12-a7e1-3128b895cad7@kernel.org \
--to=srini@kernel.org \
--cc=arnd@arndb.de \
--cc=cosmin-gabriel.tanislav.xa@renesas.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=yoshihiro.shimoda.uh@renesas.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®