netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
	"Saeed Mahameed" <saeedm@nvidia.com>
Subject: [pull request][net 0/4] mlx5 fixes 2020-12-01
Date: Wed, 2 Dec 2020 20:39:42 -0800	[thread overview]
Message-ID: <20201203043946.235385-1-saeedm@nvidia.com> (raw)

Hi Jakub,

This series introduces some fixes to mlx5 driver.
Please pull and let me know if there is any problem.

For the DR steering patch I will need it in net-next as well, I would
appreciate it if you will take this small series before your pr to linus.

For -stable v5.4:
 ('net/mlx5: DR, Proper handling of unsupported Connect-X6DX SW steering')

For -stable v5.8
 ('net/mlx5: Fix wrong address reclaim when command interface is down')

For -stable v5.9
 ('net: mlx5e: fix fs_tcp.c build when IPV6 is not enabled')

Thanks,
Saeed.

---
The following changes since commit 14483cbf040fcb38113497161088a1ce8ce5d713:

  net: broadcom CNIC: requires MMU (2020-12-01 11:44:02 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5-fixes-2020-12-01

for you to fetch changes up to c20289e64bfc0fc4bca0242d60839b9ca2e28e64:

  net/mlx5: DR, Proper handling of unsupported Connect-X6DX SW steering (2020-12-01 15:02:59 -0800)

----------------------------------------------------------------
mlx5-fixes-2020-12-01

----------------------------------------------------------------
Eran Ben Elisha (1):
      net/mlx5: Fix wrong address reclaim when command interface is down

Randy Dunlap (1):
      net: mlx5e: fix fs_tcp.c build when IPV6 is not enabled

Tariq Toukan (1):
      net/mlx5e: kTLS, Enforce HW TX csum offload with kTLS

Yevgeny Kliteynik (1):
      net/mlx5: DR, Proper handling of unsupported Connect-X6DX SW steering

 .../ethernet/mellanox/mlx5/core/en_accel/fs_tcp.c  |  2 ++
 drivers/net/ethernet/mellanox/mlx5/core/en_tx.c    | 22 +++++++++++++++-------
 .../net/ethernet/mellanox/mlx5/core/pagealloc.c    | 21 +++++++++++++++++++--
 .../ethernet/mellanox/mlx5/core/steering/dr_cmd.c  |  1 +
 .../mellanox/mlx5/core/steering/dr_domain.c        |  5 +++++
 .../mellanox/mlx5/core/steering/dr_types.h         |  1 +
 include/linux/mlx5/mlx5_ifc.h                      |  9 ++++++++-
 7 files changed, 51 insertions(+), 10 deletions(-)

             reply	other threads:[~2020-12-03  4:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03  4:39 Saeed Mahameed [this message]
2020-12-03  4:39 ` [net 1/4] net/mlx5: Fix wrong address reclaim when command interface is down Saeed Mahameed
2020-12-03  4:39 ` [net 2/4] net: mlx5e: fix fs_tcp.c build when IPV6 is not enabled Saeed Mahameed
2020-12-03  4:39 ` [net 3/4] net/mlx5e: kTLS, Enforce HW TX csum offload with kTLS Saeed Mahameed
2020-12-03  4:39 ` [net 4/4] net/mlx5: DR, Proper handling of unsupported Connect-X6DX SW steering Saeed Mahameed
2020-12-03 18:52 ` [pull request][net 0/4] mlx5 fixes 2020-12-01 Jakub Kicinski
2020-12-03 19:16   ` Jakub Kicinski
2020-12-03 19:50     ` Saeed Mahameed

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=20201203043946.235385-1-saeedm@nvidia.com \
    --to=saeedm@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).