From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: netdev@vger.kernel.org
Subject: Re: [pull request][net-next 0/9] Mellanox, mlx5 updates 2019-05-31
Date: Mon, 03 Jun 2019 13:43:26 -0700 (PDT) [thread overview]
Message-ID: <20190603.134326.372323582905007545.davem@davemloft.net> (raw)
In-Reply-To: <20190531200838.25184-1-saeedm@mellanox.com>
From: Saeed Mahameed <saeedm@mellanox.com>
Date: Fri, 31 May 2019 20:09:19 +0000
> This series adds misc updates to mlx5 driver.
> For more information please see tag log below.
>
> Please pull and let me know if there is any problem.
>
> Please note that the series starts with a merge of mlx5-next branch,
> to resolve and avoid dependency with rdma tree.
Pulled, thanks.
prev parent reply other threads:[~2019-06-03 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 20:09 [pull request][net-next 0/9] Mellanox, mlx5 updates 2019-05-31 Saeed Mahameed
2019-05-31 20:09 ` [net-next 1/9] net/mlx5e: Generalize vport type in vport representor Saeed Mahameed
2019-05-31 20:09 ` [net-next 2/9] net/mlx5e: Allow matching only enc_key_id/enc_dst_port for decapsulation action Saeed Mahameed
2019-05-31 20:09 ` [net-next 3/9] net/mlx5e: Enable setting multiple match criteria for flow group Saeed Mahameed
2019-05-31 20:09 ` [net-next 4/9] net/mlx5: Geneve, Manage Geneve TLV options Saeed Mahameed
2019-05-31 20:09 ` [net-next 5/9] net/mlx5e: Geneve, Keep tunnel info as pointer to the original struct Saeed Mahameed
2019-05-31 20:09 ` [net-next 6/9] net/mlx5e: Rearrange tc tunnel code in a modular way Saeed Mahameed
2019-05-31 20:09 ` [net-next 7/9] net/mlx5e: Geneve, Add support for encap/decap flows offload Saeed Mahameed
2019-05-31 20:09 ` [net-next 8/9] net/mlx5e: Use termination table for VLAN push actions Saeed Mahameed
2019-05-31 20:09 ` [net-next 9/9] net/mlx5e: TX, Improve performance under GSO workload Saeed Mahameed
2019-06-03 20:43 ` David Miller [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=20190603.134326.372323582905007545.davem@davemloft.net \
--to=davem@davemloft.net \
--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).