From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Aharon Landau <aharonl@nvidia.com>,
linux-rdma@vger.kernel.org, Maor Gottlieb <maorg@mellanox.com>,
Mark Bloch <mbloch@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [PATCH rdma-next 0/5] Set of fixes
Date: Wed, 13 Jan 2021 14:16:58 +0200 [thread overview]
Message-ID: <20210113121703.559778-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Small set of fixes for -next, only Aharon's fix has potential to be
taken to the -rc.
Thanks
Aharon Landau (1):
RDMA/umem: Avoid undefined behavior of rounddown_pow_of_two
Mark Bloch (1):
RDMA/mlx5: Fix wrong free of blue flame register on error
Parav Pandit (3):
IB/mlx5: Fix error unwinding when set_has_smi_cap fails
IB/mlx5: Add mutex destroy call to cap_mask_mutex mutex
IB/mlx5: Make function static
drivers/infiniband/core/umem.c | 2 +-
drivers/infiniband/hw/mlx5/mad.c | 4 ++--
drivers/infiniband/hw/mlx5/main.c | 15 +++++++--------
drivers/infiniband/hw/mlx5/mlx5_ib.h | 2 --
4 files changed, 10 insertions(+), 13 deletions(-)
--
2.29.2
next reply other threads:[~2021-01-13 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 12:16 Leon Romanovsky [this message]
2021-01-13 12:16 ` [PATCH rdma-next 1/5] RDMA/umem: Avoid undefined behavior of rounddown_pow_of_two Leon Romanovsky
2021-01-13 12:17 ` [PATCH rdma-next 2/5] IB/mlx5: Fix error unwinding when set_has_smi_cap fails Leon Romanovsky
2021-01-13 12:17 ` [PATCH rdma-next 3/5] IB/mlx5: Add mutex destroy call to cap_mask_mutex mutex Leon Romanovsky
2021-01-13 12:17 ` [PATCH rdma-next 4/5] IB/mlx5: Make function static Leon Romanovsky
2021-01-13 12:17 ` [PATCH rdma-next 5/5] RDMA/mlx5: Fix wrong free of blue flame register on error Leon Romanovsky
2021-01-14 17:04 ` [PATCH rdma-next 0/5] Set of fixes Jason Gunthorpe
2021-01-14 17:36 ` Leon Romanovsky
2021-01-20 0:15 ` Jason Gunthorpe
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=20210113121703.559778-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=aharonl@nvidia.com \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@mellanox.com \
--cc=mbloch@nvidia.com \
--cc=parav@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.