netdev - Re: [patch net-next v3 01/12] nfp: register devlink port before netdev

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]

Message-ID: <20190327105608.5db94f52@cakuba.netronome.com>
Date:   Wed, 27 Mar 2019 10:56:08 -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 v3 01/12] nfp: register devlink port before
 netdev

On Wed, 27 Mar 2019 16:19:47 +0100, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@...lanox.com>
> 
> Change the init/fini flow and register devlink port instance before
> netdev. Now it is needed for correct behavior of phys_port_name
> generation, but in general it makes sense to register devlink port
> first.
> 
> Signed-off-by: Jiri Pirko <jiri@...lanox.com>

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