netdev - Re: [patch net-next v2 10/12] nfp: do not handle nn->port defined case in nfp_net_get_phys_port

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 for Android: free password hash cracker in your pocket

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

Date:   Tue, 26 Mar 2019 13:31:57 -0700
From:   Jakub Kicinski <jakub.kicinski@...ronome.com>
To:     Jiri Pirko <jiri@...nulli.us>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, mlxsw@...lanox.com,
        idosch@...lanox.com, f.fainelli@...il.com, andrew@...n.ch,
        vivien.didelot@...il.com, michael.chan@...adcom.com
Subject: Re: [patch net-next v2 10/12] nfp: do not handle nn->port defined
 case in nfp_net_get_phys_port_name()

On Tue, 26 Mar 2019 13:03:05 +0100, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@...lanox.com>
> 
> If nn->port is defined it means that devlink_port has been registered
> for this port as well. Devlink core is handling the port name
> formatting.
> 
> Signed-off-by: Jiri Pirko <jiri@...lanox.com>

Reviewed-by: Jakub Kicinski <jakub.kicinski@...ronome.com>