From: Saeed Mahameed <saeedm@mellanox.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Saeed Mahameed <saeedm@mellanox.com>
Subject: [pull request][net 0/3] Mellanox, mlx5 fixes 2019-07-15
Date: Mon, 15 Jul 2019 20:09:53 +0000 [thread overview]
Message-ID: <20190715200940.31799-1-saeedm@mellanox.com> (raw)
Hi Dave,
This pull request provides mlx5 TC flower and tunnel fixes for kernel 5.2
from Eli and Vlad.
Please pull and let me know if there is any problem.
Thanks,
Saeed.
---
The following changes since commit f384e62a82ba5d85408405fdd6aeff89354deaa9:
ISDN: hfcsusb: checking idx of ep configuration (2019-07-15 11:10:31 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5-fixes-2019-07-15
for you to fetch changes up to 3d144578c91a2db417923ba905ce7a84ce0c274b:
net/mlx5e: Allow dissector meta key in tc flower (2019-07-15 13:04:04 -0700)
----------------------------------------------------------------
mlx5-fixes-2019-07-15
----------------------------------------------------------------
Eli Cohen (1):
net/mlx5e: Verify encapsulation is supported
Vlad Buslov (2):
net/mlx5e: Rely on filter_dev instead of dissector keys for tunnels
net/mlx5e: Allow dissector meta key in tc flower
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
next reply other threads:[~2019-07-15 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 20:09 Saeed Mahameed [this message]
2019-07-15 20:09 ` [net 1/3] net/mlx5e: Verify encapsulation is supported Saeed Mahameed
2019-07-15 20:09 ` [net 2/3] net/mlx5e: Rely on filter_dev instead of dissector keys for tunnels Saeed Mahameed
2019-07-15 20:09 ` [net 3/3] net/mlx5e: Allow dissector meta key in tc flower Saeed Mahameed
2019-07-16 0:20 ` [pull request][net 0/3] Mellanox, mlx5 fixes 2019-07-15 David Miller
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=20190715200940.31799-1-saeedm@mellanox.com \
--to=saeedm@mellanox.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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