lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <ZWmN7ifRPjuxK7f0@nanopsycho> Date: Fri, 1 Dec 2023 08:40:30 +0100 From: Jiri Pirko <jiri@...nulli.us> To: Andrew Lunn <andrew@...n.ch> Cc: "Bahadur, Sachin" <sachin.bahadur@...el.com>, "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org> Subject: Re: [PATCH iwl-next v2] ice: Print NIC FW version during init Thu, Nov 30, 2023 at 07:13:11PM CET, andrew@...n.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 > >
Powered by blists - more mailing lists