From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Edward Srouji <edwards@nvidia.com>,
linux-rdma@vger.kernel.org, Maor Gottlieb <maorg@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>,
Michael Guralnik <michaelgur@nvidia.com>,
Shay Drory <shayd@nvidia.com>
Subject: [PATCH rdma-rc 0/3] Batch of mlx5_ib fixes
Date: Wed, 20 Sep 2023 13:01:53 +0300 [thread overview]
Message-ID: <cover.1695203958.git.leonro@nvidia.com> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Hi,
This patchset is combination of various mlx5_ib fixes.
Thanks
Hamdan Igbaria (1):
RDMA/mlx5: Fix mutex unlocking on error flow for steering anchor
creation
Michael Guralnik (1):
RDMA/mlx5: Fix assigning access flags to cache mkeys
Shay Drory (1):
RDMA/mlx5: Fix NULL string error
drivers/infiniband/hw/mlx5/fs.c | 2 +-
drivers/infiniband/hw/mlx5/main.c | 2 +-
drivers/infiniband/hw/mlx5/mr.c | 3 ++-
3 files changed, 4 insertions(+), 3 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-20 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 10:01 Leon Romanovsky [this message]
2023-09-20 10:01 ` [PATCH rdma-rc 1/3] RDMA/mlx5: Fix assigning access flags to cache mkeys Leon Romanovsky
2023-09-20 10:01 ` [PATCH rdma-rc 2/3] RDMA/mlx5: Fix mutex unlocking on error flow for steering anchor creation Leon Romanovsky
2023-09-20 10:01 ` [PATCH rdma-rc 3/3] RDMA/mlx5: Fix NULL string error Leon Romanovsky
2023-09-26 9:30 ` [PATCH rdma-rc 0/3] Batch of mlx5_ib fixes Leon Romanovsky
-- strict thread matches above, loose matches on Subject: below --
2025-06-16 9:14 Leon Romanovsky
2025-06-25 7:45 ` 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.1695203958.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=edwards@nvidia.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=michaelgur@nvidia.com \
--cc=shayd@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.