netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Chiara Meiohas <cmeiohas@nvidia.com>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-rdma@vger.kernel.org,
	Michael Guralnik <michaelgur@nvidia.com>,
	netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Tariq Toukan <tariqt@nvidia.com>
Subject: [PATCH rdma-next 0/3] Fixes to set_netdev/get_netdev flow
Date: Thu, 31 Oct 2024 15:36:49 +0200	[thread overview]
Message-ID: <cover.1730381292.git.leon@kernel.org> (raw)

This series fixes the set_netdev/get_netdev flow in mlx5 drive around LAG.

Thanks

Chiara Meiohas (3):
  RDMA/mlx5: Call dev_put() after the blocking notifier
  RDMA/core: Implement RoCE GID port rescan and export delete function
  RDMA/mlx5: Ensure active slave attachment to the bond IB device

 drivers/infiniband/core/roce_gid_mgmt.c       | 30 ++++++++++++++++---
 drivers/infiniband/hw/mlx5/main.c             | 29 +++++++++++-------
 .../net/ethernet/mellanox/mlx5/core/lag/lag.c | 12 ++++++++
 include/rdma/ib_verbs.h                       |  3 ++
 4 files changed, 59 insertions(+), 15 deletions(-)

-- 
2.46.2


             reply	other threads:[~2024-10-31 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 13:36 Leon Romanovsky [this message]
2024-10-31 13:36 ` [PATCH mlx5-next 1/3] RDMA/mlx5: Call dev_put() after the blocking notifier Leon Romanovsky
2024-10-31 13:36 ` [PATCH mlx5-next 3/3] RDMA/mlx5: Ensure active slave attachment to the bond IB device Leon Romanovsky
2024-11-04  8:43 ` [PATCH rdma-next 0/3] Fixes to set_netdev/get_netdev flow Leon Romanovsky

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=cover.1730381292.git.leon@kernel.org \
    --to=leon@kernel.org \
    --cc=cmeiohas@nvidia.com \
    --cc=edumazet@google.com \
    --cc=jgg@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=michaelgur@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@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 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).