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/7] Mellanox, mlx5 fixes 2019-09-24
Date: Tue, 24 Sep 2019 09:41:18 +0000 [thread overview]
Message-ID: <20190924094047.15915-1-saeedm@mellanox.com> (raw)
Hi Dave,
This series introduces some fixes to mlx5 driver.
For more information please see tag log below.
Please pull and let me know if there is any problem.
For -stable v4.10:
('net/mlx5e: Fix traffic duplication in ethtool steering')
For -stable v4.19:
('net/mlx5: Add device ID of upcoming BlueField-2')
For -stable v5.3:
('net/mlx5e: Fix matching on tunnel addresses type')
Thanks,
Saeed.
---
The following changes since commit 34b4688425d9841a19a15fa6ae2bfc12a372650f:
net: dsa: Use the correct style for SPDX License Identifier (2019-09-22 15:25:08 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5-fixes-2019-09-24
for you to fetch changes up to fe1587a7de94912ed75ba5ddbfabf0741f9f8239:
net/mlx5e: Fix matching on tunnel addresses type (2019-09-24 12:38:08 +0300)
----------------------------------------------------------------
mlx5-fixes-2019-09-24
----------------------------------------------------------------
Alaa Hleihel (1):
net/mlx5: DR, Allow matching on vport based on vhca_id
Alex Vesker (2):
net/mlx5: DR, Remove redundant vport number from action
net/mlx5: DR, Fix getting incorrect prev node in ste_free
Bodong Wang (1):
net/mlx5: Add device ID of upcoming BlueField-2
Dmytro Linkin (1):
net/mlx5e: Fix matching on tunnel addresses type
Saeed Mahameed (1):
net/mlx5e: Fix traffic duplication in ethtool steering
Yevgeny Kliteynik (1):
net/mlx5: DR, Fix SW steering HW bits and definitions
.../ethernet/mellanox/mlx5/core/en_fs_ethtool.c | 4 +-
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | 89 +++++++++++++---------
drivers/net/ethernet/mellanox/mlx5/core/main.c | 1 +
.../mellanox/mlx5/core/steering/dr_action.c | 4 +-
.../mellanox/mlx5/core/steering/dr_matcher.c | 13 ++--
.../ethernet/mellanox/mlx5/core/steering/dr_rule.c | 2 +-
.../ethernet/mellanox/mlx5/core/steering/dr_ste.c | 50 ++++++++----
.../mellanox/mlx5/core/steering/dr_types.h | 7 +-
include/linux/mlx5/mlx5_ifc.h | 28 +++----
9 files changed, 119 insertions(+), 79 deletions(-)
next reply other threads:[~2019-09-24 9:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 9:41 Saeed Mahameed [this message]
2019-09-24 9:41 ` [net 1/7] net/mlx5: DR, Fix SW steering HW bits and definitions Saeed Mahameed
2019-09-24 9:41 ` [net 2/7] net/mlx5: DR, Remove redundant vport number from action Saeed Mahameed
2019-09-24 9:41 ` [net 3/7] net/mlx5: DR, Fix getting incorrect prev node in ste_free Saeed Mahameed
2019-09-24 9:41 ` [net 4/7] net/mlx5: DR, Allow matching on vport based on vhca_id Saeed Mahameed
2019-09-24 9:41 ` [net 5/7] net/mlx5: Add device ID of upcoming BlueField-2 Saeed Mahameed
2019-09-24 9:41 ` [net 6/7] net/mlx5e: Fix traffic duplication in ethtool steering Saeed Mahameed
2019-09-24 9:41 ` [net 7/7] net/mlx5e: Fix matching on tunnel addresses type Saeed Mahameed
2019-09-24 9:51 ` [pull request][net 0/7] Mellanox, mlx5 fixes 2019-09-24 Saeed Mahameed
2019-09-26 7:16 ` 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=20190924094047.15915-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