[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190328.125621.1391948529457599809.davem@davemloft.net>
Date: Thu, 28 Mar 2019 12:56:21 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jiri@...nulli.us
Cc: netdev@...r.kernel.org, mlxsw@...lanox.com, idosch@...lanox.com,
jakub.kicinski@...ronome.com, f.fainelli@...il.com, andrew@...n.ch,
vivien.didelot@...il.com, michael.chan@...adcom.com
Subject: Re: [patch net-next v4 00/12] net: call for phys_port_name into
devlink directly if possible
From: Jiri Pirko <jiri@...nulli.us>
Date: Thu, 28 Mar 2019 13:56:34 +0100
> From: Jiri Pirko <jiri@...lanox.com>
>
> phys_port_name may be assembled by a helper in devlink. It is currently
> the case only for mlxsw driver. Benefit from the get_devlink_port ndo
> and call into devlink directly from dev_get_phys_port_name(). That saves
> the trip to the driver, simplifies the code and makes it similar to
> recently introduced ethtool-devlink compat helpers.
>
> Move bnxt, partly nfp and dsa to let devlink core generate the name too.
Series applied, thanks Jiri.
Powered by blists - more mailing lists