From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] nvmem: fix dev_dbg(unregistered_device, ...)
Date: Mon, 28 Jun 2021 14:52:45 +0200 [thread overview]
Message-ID: <20210628125245.GN9782@pengutronix.de> (raw)
In-Reply-To: <20210628054420.31051-1-a.fatoum@pengutronix.de>
On Mon, Jun 28, 2021 at 07:44:20AM +0200, Ahmad Fatoum wrote:
> The format string already prints the future name of the NVMEM device, so
> use the parent name as qualifier for the dev_dbg call.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> drivers/nvmem/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks
Sascha
>
> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
> index ae9c965c25e2..4e558e165063 100644
> --- a/drivers/nvmem/core.c
> +++ b/drivers/nvmem/core.c
> @@ -224,7 +224,7 @@ struct nvmem_device *nvmem_register(const struct nvmem_config *config)
> dev_set_name(&nvmem->dev, config->name);
> nvmem->dev.id = DEVICE_ID_DYNAMIC;
>
> - dev_dbg(&nvmem->dev, "Registering nvmem device %s\n", config->name);
> + dev_dbg(nvmem->dev.parent, "Registering nvmem device %s\n", config->name);
>
> rval = register_device(&nvmem->dev);
> if (rval) {
> --
> 2.30.2
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2021-06-28 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 5:44 Ahmad Fatoum
2021-06-28 12:52 ` Sascha Hauer [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=20210628125245.GN9782@pengutronix.de \
--to=sha@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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