netdev - Re: [PATCH net-next 00/11] mlxsw: extend line card model by devices and info

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 23 May 2022 11:42:07 +0200
From:   Jiri Pirko <jiri@...nulli.us>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Ido Schimmel <idosch@...sch.org>, Ido Schimmel <idosch@...dia.com>,
        netdev@...r.kernel.org, davem@...emloft.net, pabeni@...hat.com,
        jiri@...dia.com, petrm@...dia.com, dsahern@...il.com,
        andrew@...n.ch, mlxsw@...dia.com
Subject: Re: [PATCH net-next 00/11] mlxsw: extend line card model by devices
 and info

First of all, sorry for delay :/


Mon, May 02, 2022 at 04:39:33PM CEST, kuba@...nel.org wrote:
>On Sat, 30 Apr 2022 08:27:35 +0200 Jiri Pirko wrote:
>> Now I just want to use this component name to target individual line
>> cards. I see it is a nice fit. Don't you think?
>
>Still on the fence.

Why?

>
>> I see that the manpage is mentioning "the component names from devlink dev info"
>> which is not actually implemented, but exactly what I proposed.
>
>How do you tie the line card to the component name? lc8_dev0 from 
>the flashing example is not present in the lc info output.

Okay, I will move it there. Makes sense.


>
>> >Please answer questions. I already complained about this once in 
>> >this thread.  
>> 
>> Sorry, I missed this one. The file IS a FW just for a SINGLE gearbox.
>
>I see.