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 Zhang <markzhang@nvidia.com>,
Michael Guralnik <michaelgur@nvidia.com>,
Or Har-Toov <ohartoov@nvidia.com>,
Tamar Mashiah <tmashiah@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>
Subject: [PATCH rdma-next 0/6] Collection of mlx5_ib fixes
Date: Thu, 25 Jan 2024 14:30:06 +0200 [thread overview]
Message-ID: <cover.1706185318.git.leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Hi,
Collection of independent fixes for mlx5_ib driver.
Thanks
Leon Romanovsky (1):
RDMA/mlx5: Fix fortify source warning while accessing Eth segment
Mark Zhang (1):
IB/mlx5: Don't expose debugfs entries for RRoCE general parameters if
not supported
Or Har-Toov (3):
RDMA/mlx5: Uncacheable mkey has neither rb_key or cache_ent
RDMA/mlx5: Change check for cacheable user mkeys
RDMA/mlx5: Adding remote atomic access flag to updatable flags
Yishai Hadas (1):
RDMA/mlx5: Relax DEVX access upon modify commands
drivers/infiniband/hw/mlx5/cong.c | 6 ++++++
drivers/infiniband/hw/mlx5/devx.c | 2 +-
drivers/infiniband/hw/mlx5/mlx5_ib.h | 2 +-
drivers/infiniband/hw/mlx5/mr.c | 18 ++++++++++--------
drivers/infiniband/hw/mlx5/wr.c | 2 +-
include/linux/mlx5/mlx5_ifc.h | 2 +-
include/linux/mlx5/qp.h | 5 ++++-
7 files changed, 24 insertions(+), 13 deletions(-)
--
2.43.0
next reply other threads:[~2024-01-25 12:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 12:30 Leon Romanovsky [this message]
2024-01-25 12:30 ` [PATCH rdma-next 1/6] RDMA/mlx5: Fix fortify source warning while accessing Eth segment Leon Romanovsky
2024-01-25 12:30 ` [PATCH rdma-next 2/6] IB/mlx5: Don't expose debugfs entries for RRoCE general parameters if not supported Leon Romanovsky
2024-01-25 12:30 ` [PATCH rdma-next 3/6] RDMA/mlx5: Relax DEVX access upon modify commands Leon Romanovsky
2024-01-25 12:30 ` [PATCH rdma-next 4/6] RDMA/mlx5: Uncacheable mkey has neither rb_key or cache_ent Leon Romanovsky
2024-01-25 12:30 ` [PATCH rdma-next 5/6] RDMA/mlx5: Change check for cacheable user mkeys Leon Romanovsky
2024-01-25 12:52 ` Junxian Huang
2024-01-25 13:30 ` Zhu Yanjun
2024-01-26 1:47 ` Junxian Huang
2024-01-25 13:38 ` Jason Gunthorpe
2024-01-25 20:02 ` Leon Romanovsky
2024-01-26 2:17 ` Zhu Yanjun
2024-01-25 12:30 ` [PATCH rdma-next 6/6] RDMA/mlx5: Adding remote atomic access flag to updatable flags 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.1706185318.git.leon@kernel.org \
--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=markzhang@nvidia.com \
--cc=michaelgur@nvidia.com \
--cc=ohartoov@nvidia.com \
--cc=tmashiah@nvidia.com \
--cc=yishaih@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