Wed, Mar 20, 2019 at 09:25:53PM CET, jakub.kicin...@netronome.com wrote:
>On Fri, 1 Mar 2019 10:04:46 -0800, Jakub Kicinski wrote:
>> Hi!
>>
>> This series is a long overdue follow up to Jiri's work on providing
>> a common .ndo_phys_port_name implementation based on devlink ports.
>
>Hi Jiri,
>
On Fri, 1 Mar 2019 10:04:46 -0800, Jakub Kicinski wrote:
> Hi!
>
> This series is a long overdue follow up to Jiri's work on providing
> a common .ndo_phys_port_name implementation based on devlink ports.
Hi Jiri,
unfortunately I need to focus on some urgent work, so I won't have time
to work o
From: Jakub Kicinski
Date: Fri, 1 Mar 2019 10:04:46 -0800
> This series is a long overdue follow up to Jiri's work on providing
> a common .ndo_phys_port_name implementation based on devlink ports.
I think this needs enough discussion still that it will have to wait
until the next merge window.
> -Original Message-
> From: netdev-ow...@vger.kernel.org On
> Behalf Of Jiri Pirko
> Sent: Saturday, March 2, 2019 4:14 AM
> To: Jakub Kicinski
> Cc: da...@davemloft.net; netdev@vger.kernel.org; oss-
> driv...@netronome.com
> Subject: Re: [PATCH net-next v2
On Sat, 2 Mar 2019 11:13:37 +0100, Jiri Pirko wrote:
> >This is the conceptual image of devlink instances:
> >
> >HOST A || HOST B
> > ||
> >PF A | V | V | V | V || PF B| V | V | V
> >
Fri, Mar 01, 2019 at 07:04:46PM CET, jakub.kicin...@netronome.com wrote:
>Hi!
>
>This series is a long overdue follow up to Jiri's work on providing
>a common .ndo_phys_port_name implementation based on devlink ports.
>
>First devlink port flavours for PF and VF ports are added, and
>registered by
