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: <YwR1URDk56l5VLDZ@nanopsycho> Date: Tue, 23 Aug 2022 08:36:01 +0200 From: Jiri Pirko <jiri@...nulli.us> To: Jakub Kicinski <kuba@...nel.org> Cc: netdev@...r.kernel.org, davem@...emloft.net, idosch@...dia.com, pabeni@...hat.com, edumazet@...gle.com, saeedm@...dia.com, jacob.e.keller@...el.com, vikas.gupta@...adcom.com, gospo@...adcom.com Subject: Re: [patch net-next v2 4/4] net: devlink: expose the info about version representing a component Tue, Aug 23, 2022 at 05:01:16AM CEST, kuba@...nel.org wrote: >On Mon, 22 Aug 2022 19:02:47 +0200 Jiri Pirko wrote: >> If certain version exposed by a driver is marked to be representing a >> component, expose this info to the user. >> >> Example: >> $ devlink dev info >> netdevsim/netdevsim10: >> driver netdevsim >> versions: >> running: >> fw.mgmt 10.20.30 >> flash_components: >> fw.mgmt > >I don't think we should add API without a clear use, let's drop this >as well. What do you mean? This just simply lists components that are possible to use with devlink dev flash. What is not clear? I don't follow.
Powered by blists - more mailing lists