[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171227.170122.256080933244367774.davem@davemloft.net>
Date: Wed, 27 Dec 2017 17:01:22 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: saeedm@...lanox.com
Cc: dledford@...hat.com, netdev@...r.kernel.org,
linux-rdma@...r.kernel.org, leonro@...lanox.com
Subject: Re: [pull request][for-next V2 00/11] Mellanox, mlx5 E-Switch
updates 2017-12-19
From: Saeed Mahameed <saeedm@...lanox.com>
Date: Sun, 24 Dec 2017 15:45:36 +0200
> Hi Dave and Doug,
>
> ==============
> This series includes updates for mlx5 E-Switch infrastructures,
> to be merged into net-next and rdma-next trees.
>
> Mark's patches provide E-Switch refactoring that generalize the mlx5
> E-Switch vf representors interfaces and data structures. The serious is
> mainly focused on moving ethernet (netdev) specific representors logic out
> of E-Switch (eswitch.c) into mlx5e representor module (en_rep.c), which
> provides better separation and allows future support for other types of vf
> representors (e.g. RDMA).
>
> Gal's patches at the end of this serious, provide a simple syntax fix and
> two other patches that handles vport ingress/egress ACL steering name
> spaces to be aligned with the Firmware/Hardware specs.
> ===============
>
> V1->V2:
> - Addressed coding style comments in patches #1 and #7
> - The series is still based on rc4, as now I see net-next is also @rc4.
>
> Please pull and let me know if there's any problem.
Pulled, thank you.
Powered by blists - more mailing lists