All of lore.kernel.org
 help / color / mirror / Atom feed
From: Drew DeVault <sir@cmpwn.com>
To: Luis Chamberlain <mcgrof@kernel.org>, linux-kernel@vger.kernel.org
Cc: Drew DeVault <sir@cmpwn.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	~sircmpwn/public-inbox@lists.sr.ht
Subject: [PATCH v2] firmware loader: log path to loaded firmwares
Date: Sun,  3 Nov 2019 13:06:46 -0500	[thread overview]
Message-ID: <20191103180646.34880-1-sir@cmpwn.com> (raw)


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>
---
v2 uses dev_dbg instead of printk(KERN_INFO)

 drivers/base/firmware_loader/main.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/base/firmware_loader/main.c b/drivers/base/firmware_loader/main.c
index bf44c79beae9..2537da43a572 100644
--- a/drivers/base/firmware_loader/main.c
+++ b/drivers/base/firmware_loader/main.c
@@ -504,6 +504,7 @@ fw_get_filesystem_firmware(struct device *device, struct fw_priv *fw_priv,
 					 path);
 			continue;
 		}
+		dev_dbg(device, "Loading firmware from %s\n", path);
 		if (decompress) {
 			dev_dbg(device, "f/w decompressing %s\n",
 				fw_priv->fw_name);
-- 
2.23.0


             reply	other threads:[~2019-11-03 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-03 18:06 Drew DeVault [this message]
2019-11-13  0:56 ` [PATCH v2] firmware loader: log path to loaded firmwares Luis Chamberlain
2019-11-13 14:05   ` Drew DeVault
2019-11-13 20:19   ` Robin H. Johnson
2019-11-13 20:50     ` Luis Chamberlain
2019-11-17 18:46       ` Drew DeVault
2019-11-17 23:47     ` [PATCH v3] firmware: log name & outcome of loaded firmware Robin H. Johnson
2019-11-18 17:53       ` 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=20191103180646.34880-1-sir@cmpwn.com \
    --to=sir@cmpwn.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=rafael@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.