From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Saeed Mahameed <saeedm@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
Jason Gunthorpe <jgg@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH mlx5-next 00/11] Mellanox, mlx5-next updates 2019-04-25
Date: Fri, 26 Apr 2019 16:01:49 -0700 [thread overview]
Message-ID: <20190426160149.73d00a6c@cakuba.netronome.com> (raw)
In-Reply-To: <20190426215732.29761-1-saeedm@mellanox.com>
On Fri, 26 Apr 2019 21:58:02 +0000, Saeed Mahameed wrote:
> Hi,
>
> This series provides misc low level updates to mlx5 core driver, to be
> shared between rdma and net-next trees.
>
> 1) From Aya: Enable general events on all physical link types and
> restrict general event handling of subtype DELAY_DROP_TIMEOUT in mlx5 rdma
> driver to ethernet links only as it was intended.
>
> 2) From Eli: Introduce low level bits for prio tag mode
>
> 3) From Maor: Low level steering updates to support RDMA RX flow
> steering and enables RoCE loopback traffic when switchdev is enabled.
>
> 4) From Vu and Parav: Two small mlx5 core cleanups
>
> 5) From Yevgeny add HW definitions of geneve offloads
>
> In case of no objections this series will be applied to mlx5-next
> branch.
I can't really speak to implications of patch 9, but otherwise seems
inoffensive from netdev perspective :)
Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
prev parent reply other threads:[~2019-04-26 23:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 21:58 [PATCH mlx5-next 00/11] Mellanox, mlx5-next updates 2019-04-25 Saeed Mahameed
2019-04-26 21:58 ` [PATCH mlx5-next 01/11] net/mlx5: E-Switch: Introduce prio tag mode Saeed Mahameed
2019-04-26 21:58 ` [PATCH mlx5-next 02/11] net/mlx5: Get rid of storing copy of device name Saeed Mahameed
2019-04-26 21:58 ` [PATCH mlx5-next 03/11] net/mlx5: Separate and generalize dma device from pci device Saeed Mahameed
2019-04-26 21:58 ` [PATCH mlx5-next 04/11] IB/mlx5: Restrict 'DELAY_DROP_TIMEOUT' subtype to Ethernet interfaces Saeed Mahameed
2019-04-26 21:58 ` [PATCH mlx5-next 05/11] net/mlx5: Enable general events on all interfaces Saeed Mahameed
2019-04-26 21:58 ` [PATCH mlx5-next 06/11] net/mlx5: Pass flow steering objects to fs_cmd Saeed Mahameed
2019-04-26 21:58 ` [PATCH mlx5-next 07/11] net/mlx5: Add support in RDMA RX steering Saeed Mahameed
2019-04-26 21:58 ` [PATCH mlx5-next 08/11] net/mlx5: Add new miss flow table action Saeed Mahameed
2019-04-26 21:58 ` [PATCH mlx5-next 09/11] net/mlx5: Eswitch, enable RoCE loopback traffic Saeed Mahameed
2019-04-27 5:49 ` Leon Romanovsky
2019-04-26 21:58 ` [PATCH mlx5-next 10/11] net/mlx5: Geneve, Add basic Geneve encap/decap flow table capabilities Saeed Mahameed
2019-04-26 21:58 ` [PATCH mlx5-next 11/11] net/mlx5: Geneve, Add flow table capabilities for Geneve decap with TLV options Saeed Mahameed
2019-04-26 23:01 ` Jakub Kicinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190426160149.73d00a6c@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).