From: Jiri Pirko <jiri@resnulli.us>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Bahadur, Sachin" <sachin.bahadur@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH iwl-next v2] ice: Print NIC FW version during init
Date: Fri, 1 Dec 2023 08:40:30 +0100 [thread overview]
Message-ID: <ZWmN7ifRPjuxK7f0@nanopsycho> (raw)
In-Reply-To: <fadae2d9-68ab-4a1a-bfe1-78d0f1c2fb13@lunn.ch>
Thu, Nov 30, 2023 at 07:13:11PM CET, andrew@lunn.ch wrote:
>> Yes, this info is available via the "devlink dev info" command.
>> Adding this info in dmesg ensures the version information is
>> available when someone is looking at the dmesg log to debug an issue.
>
>Ideally you would train your users to use devlink info, since you get
>more useful information, and it should work for any vendors NIC, not
>just Intel which is spamming the log with firmware versions.
+1
>
> Andrew
>
>
prev parent reply other threads:[~2023-12-01 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 17:56 [PATCH iwl-next v2] ice: Print NIC FW version during init Sachin Bahadur
2023-11-30 15:56 ` Andrew Lunn
2023-11-30 17:08 ` Bahadur, Sachin
2023-11-30 18:13 ` Andrew Lunn
2023-12-01 7:40 ` Jiri Pirko [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=ZWmN7ifRPjuxK7f0@nanopsycho \
--to=jiri@resnulli.us \
--cc=andrew@lunn.ch \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=sachin.bahadur@intel.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