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-next 00/15] mlx5 updates 2021-03-11
Date: Thu, 11 Mar 2021 14:37:08 -0800	[thread overview]
Message-ID: <20210311223723.361301-1-saeed@kernel.org> (raw)

From: Saeed Mahameed <saeedm@nvidia.com>

Hi Dave, Jakub,

This series provides some cleanups to mlx5 driver
For more information please see tag log below.

Please pull and let me know if there is any problem.

Thanks,
Saeed.

---
The following changes since commit 34bb975126419e86bc3b95e200dc41de6c6ca69c:

  net: fddi: skfp: Mundane typo fixes throughout the file smt.h (2021-03-10 15:42:22 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5-updates-2021-03-11

for you to fetch changes up to 9f4d9283388d9069dcf4d68ae9a212d7f0e6a985:

  net/mlx5e: Alloc flow spec using kvzalloc instead of kzalloc (2021-03-11 14:35:15 -0800)

----------------------------------------------------------------
mlx5-updates-2021-03-11

Cleanups for mlx5 driver

1) Fix build warnings form Arnd and Vlad
2) Leon improves locking for driver load/unload flows
3) From Roi, Lockdep false dependency warning
4) Other trivial cleanups

----------------------------------------------------------------
Arnd Bergmann (1):
      net/mlx5e: fix mlx5e_tc_tun_update_header_ipv6 dummy definition

Eli Cohen (1):
      net/mlx5: Avoid unnecessary operation

Leon Romanovsky (5):
      net/mlx5: Remove impossible checks of interface state
      net/mlx5: Separate probe vs. reload flows
      net/mlx5: Remove second FW tracer check
      net/mlx5: Don't rely on interface state bit
      net/mlx5: Check returned value from health recover sequence

Roi Dayan (3):
      net/mlx5e: CT, Avoid false lock dependency warning
      net/mlx5: SF, Fix return type
      net/mlx5e: Alloc flow spec using kvzalloc instead of kzalloc

Saeed Mahameed (3):
      net/mlx5: Don't skip vport check
      net/mlx5e: mlx5_tc_ct_init does not fail
      net/mlx5e: rep: Improve reg_cX conditions

Vlad Buslov (2):
      net/mlx5e: Add missing include
      net/mlx5: Fix indir stable stubs

 drivers/net/ethernet/mellanox/mlx5/core/devlink.c  |   6 +-
 .../ethernet/mellanox/mlx5/core/diag/fw_tracer.c   |   5 +-
 .../net/ethernet/mellanox/mlx5/core/en/rep/tc.c    |   8 +-
 drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c |  24 +++-
 .../net/ethernet/mellanox/mlx5/core/en/tc_tun.h    |  10 +-
 .../ethernet/mellanox/mlx5/core/en/tc_tun_encap.c  |   1 +
 .../mellanox/mlx5/core/en_accel/ipsec_fs.c         |   4 +-
 drivers/net/ethernet/mellanox/mlx5/core/en_tc.c    |   8 --
 .../ethernet/mellanox/mlx5/core/esw/devlink_port.c |   2 +-
 .../ethernet/mellanox/mlx5/core/esw/indir_table.h  |   6 +-
 drivers/net/ethernet/mellanox/mlx5/core/eswitch.c  |   6 +
 .../ethernet/mellanox/mlx5/core/eswitch_offloads.c |  10 +-
 drivers/net/ethernet/mellanox/mlx5/core/fs_core.c  |   6 +-
 drivers/net/ethernet/mellanox/mlx5/core/fw_reset.c |  13 +-
 drivers/net/ethernet/mellanox/mlx5/core/health.c   |   6 +-
 drivers/net/ethernet/mellanox/mlx5/core/lib/gid.c  |   5 -
 drivers/net/ethernet/mellanox/mlx5/core/main.c     | 143 ++++++++++++++-------
 .../net/ethernet/mellanox/mlx5/core/mlx5_core.h    |   8 +-
 .../net/ethernet/mellanox/mlx5/core/sf/dev/dev.h   |   2 +-
 .../ethernet/mellanox/mlx5/core/sf/dev/driver.c    |  14 +-
 20 files changed, 169 insertions(+), 118 deletions(-)

             reply	other threads:[~2021-03-11 22:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 22:37 Saeed Mahameed [this message]
2021-03-11 22:37 ` [net-next 01/15] net/mlx5: Don't skip vport check Saeed Mahameed
2021-03-12  0:30   ` patchwork-bot+netdevbpf
2021-03-11 22:37 ` [net-next 02/15] net/mlx5: Remove impossible checks of interface state Saeed Mahameed
2021-03-11 22:37 ` [net-next 03/15] net/mlx5: Separate probe vs. reload flows Saeed Mahameed
2021-03-11 22:37 ` [net-next 04/15] net/mlx5: Remove second FW tracer check Saeed Mahameed
2021-03-11 22:37 ` [net-next 05/15] net/mlx5: Don't rely on interface state bit Saeed Mahameed
2021-03-11 22:37 ` [net-next 06/15] net/mlx5: Check returned value from health recover sequence Saeed Mahameed
2021-03-11 22:37 ` [net-next 07/15] net/mlx5e: CT, Avoid false lock dependency warning Saeed Mahameed
2021-03-11 22:37 ` [net-next 08/15] net/mlx5e: fix mlx5e_tc_tun_update_header_ipv6 dummy definition Saeed Mahameed
2021-03-11 22:37 ` [net-next 09/15] net/mlx5e: Add missing include Saeed Mahameed
2021-03-11 22:37 ` [net-next 10/15] net/mlx5: Fix indir stable stubs Saeed Mahameed
2021-03-11 22:37 ` [net-next 11/15] net/mlx5e: mlx5_tc_ct_init does not fail Saeed Mahameed
2021-03-11 22:37 ` [net-next 12/15] net/mlx5: SF, Fix return type Saeed Mahameed
2021-03-11 22:37 ` [net-next 13/15] net/mlx5e: rep: Improve reg_cX conditions Saeed Mahameed
2021-03-11 22:37 ` [net-next 14/15] net/mlx5: Avoid unnecessary operation Saeed Mahameed
2021-03-11 22:37 ` [net-next 15/15] net/mlx5e: Alloc flow spec using kvzalloc instead of kzalloc 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=20210311223723.361301-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.