From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Drew DeVault <sir@cmpwn.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
~sircmpwn/public-inbox@lists.sr.ht
Subject: Re: [PATCH] firmware loader: log path to loaded firmwares
Date: Sun, 3 Nov 2019 18:50:11 +0100 [thread overview]
Message-ID: <20191103175011.GA751209@kroah.com> (raw)
In-Reply-To: <20191103173837.1861-1-sir@cmpwn.com>
On Sun, Nov 03, 2019 at 12:38:38PM -0500, Drew DeVault wrote:
> This is useful for users who are trying to identify the firmwares in use
> on their system.
>
> Signed-off-by: Drew DeVault <sir@cmpwn.com>
> ---
> drivers/base/firmware_loader/main.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/base/firmware_loader/main.c b/drivers/base/firmware_loader/main.c
> index bf44c79beae9..139d40a2f423 100644
> --- a/drivers/base/firmware_loader/main.c
> +++ b/drivers/base/firmware_loader/main.c
> @@ -34,6 +34,7 @@
> #include <linux/reboot.h>
> #include <linux/security.h>
> #include <linux/xz.h>
> +#include <linux/kernel.h>
>
> #include <generated/utsrelease.h>
>
> @@ -504,6 +505,7 @@ fw_get_filesystem_firmware(struct device *device, struct fw_priv *fw_priv,
> path);
> continue;
> }
> + printk(KERN_INFO "Loading firmware from %s\n", path);
And it's totally noisy :(
Also, if you have a 'struct device' you should always use the dev_*()
calls instead, which will show you exactly what device is asking for
what.
Please just make this a debug call, that way you can turn it on
dynamically if you really want to see what firmware is attempting to be
loaded.
thanks,
greg k-h
next prev parent reply other threads:[~2019-11-03 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 17:38 [PATCH] firmware loader: log path to loaded firmwares Drew DeVault
2019-11-03 17:50 ` Greg Kroah-Hartman [this message]
2019-11-03 17:55 ` Drew DeVault
2019-11-03 18:04 ` Greg Kroah-Hartman
2019-11-03 18:06 ` Drew DeVault
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=20191103175011.GA751209@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=rafael@kernel.org \
--cc=sir@cmpwn.com \
--cc=~sircmpwn/public-inbox@lists.sr.ht \
/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