All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeed@kernel.org>
To: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>
Subject: [pull request][net 0/5] mlx5 fixes 2021-10-20
Date: Wed, 20 Oct 2021 10:56:22 -0700	[thread overview]
Message-ID: <20211020175627.269138-1-saeed@kernel.org> (raw)

From: Saeed Mahameed <saeedm@nvidia.com>

Hi Dave and Jakub,

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

Thanks,
Saeed.

---
The following changes since commit 4225fea1cb28370086e17e82c0f69bec2779dca0:

  ptp: Fix possible memory leak in ptp_clock_register() (2021-10-20 14:44:33 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5-fixes-2021-10-20

for you to fetch changes up to 1d000323940137332d4d62c6332b6daf5f07aba7:

  net/mlx5e: IPsec: Fix work queue entry ethernet segment checksum flags (2021-10-20 10:42:51 -0700)

----------------------------------------------------------------
mlx5-fixes-2021-10-20

----------------------------------------------------------------
Dmytro Linkin (1):
      net/mlx5: E-switch, Return correct error code on group creation failure

Emeel Hakim (2):
      net/mlx5e: IPsec: Fix a misuse of the software parser's fields
      net/mlx5e: IPsec: Fix work queue entry ethernet segment checksum flags

Maor Dickman (1):
      net/mlx5: Lag, change multipath and bonding to be mutually exclusive

Moshe Shemesh (1):
      net/mlx5e: Fix vlan data lost during suspend flow

 drivers/net/ethernet/mellanox/mlx5/core/en/fs.h    |  3 ++
 .../net/ethernet/mellanox/mlx5/core/en/tc_tun.c    |  2 +
 .../mellanox/mlx5/core/en_accel/ipsec_rxtx.c       | 51 ++++++++++++----------
 drivers/net/ethernet/mellanox/mlx5/core/en_fs.c    | 28 +++++++-----
 drivers/net/ethernet/mellanox/mlx5/core/en_main.c  |  7 +++
 drivers/net/ethernet/mellanox/mlx5/core/en_tc.c    |  2 +
 drivers/net/ethernet/mellanox/mlx5/core/en_tx.c    | 20 +++++----
 drivers/net/ethernet/mellanox/mlx5/core/esw/qos.c  |  7 ++-
 drivers/net/ethernet/mellanox/mlx5/core/lag.c      |  4 ++
 drivers/net/ethernet/mellanox/mlx5/core/lag_mp.c   | 13 +++---
 drivers/net/ethernet/mellanox/mlx5/core/lag_mp.h   |  2 +
 include/linux/mlx5/driver.h                        |  1 -
 12 files changed, 85 insertions(+), 55 deletions(-)

             reply	other threads:[~2021-10-20 17:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 17:56 Saeed Mahameed [this message]
2021-10-20 17:56 ` [net 1/5] net/mlx5: Lag, change multipath and bonding to be mutually exclusive Saeed Mahameed
2021-10-21 11:20   ` patchwork-bot+netdevbpf
2021-10-20 17:56 ` [net 2/5] net/mlx5: E-switch, Return correct error code on group creation failure Saeed Mahameed
2021-10-20 17:56 ` [net 3/5] net/mlx5e: Fix vlan data lost during suspend flow Saeed Mahameed
2021-10-20 17:56 ` [net 4/5] net/mlx5e: IPsec: Fix a misuse of the software parser's fields Saeed Mahameed
2021-10-20 17:56 ` [net 5/5] net/mlx5e: IPsec: Fix work queue entry ethernet segment checksum flags 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=20211020175627.269138-1-saeed@kernel.org \
    --to=saeed@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.