From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
linux-rdma@vger.kernel.org, Mark Zhang <markzhang@nvidia.com>,
Michael Guralnik <michaelgur@nvidia.com>,
Or Har-Toov <ohartoov@nvidia.com>
Subject: [PATCH rdma-next 0/4] Various core fixes
Date: Mon, 7 Nov 2022 10:51:32 +0200 [thread overview]
Message-ID: <cover.1667810736.git.leonro@nvidia.com> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Batch unrelated fixes.
Mark Zhang (3):
RDMA/restrack: Release MR restrack when delete
RDMA/core: Make sure "ib_port" is valid when access sysfs node
RDMA/nldev: Return "-EAGAIN" if the cm_id isn't from expected port
Or Har-Toov (1):
RDMA/nldev: Use __nlmsg_put instead nlmsg_put
drivers/infiniband/core/nldev.c | 110 ++++++++++++++---------------
drivers/infiniband/core/restrack.c | 2 -
drivers/infiniband/core/sysfs.c | 17 +++--
3 files changed, 64 insertions(+), 65 deletions(-)
--
2.38.1
next reply other threads:[~2022-11-07 8:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 8:51 Leon Romanovsky [this message]
2022-11-07 8:51 ` [PATCH rdma-next 1/4] RDMA/nldev: Use __nlmsg_put instead nlmsg_put Leon Romanovsky
2022-11-09 19:15 ` Jason Gunthorpe
2022-11-13 7:19 ` Leon Romanovsky
2022-11-14 14:17 ` Jason Gunthorpe
2022-11-15 7:52 ` Leon Romanovsky
2022-11-07 8:51 ` [PATCH rdma-next 2/4] RDMA/restrack: Release MR restrack when delete Leon Romanovsky
2022-11-09 19:08 ` Jason Gunthorpe
2022-11-10 9:35 ` Leon Romanovsky
2022-11-10 19:29 ` Jason Gunthorpe
2022-11-10 19:39 ` Leon Romanovsky
2022-11-10 19:47 ` Jason Gunthorpe
2022-11-07 8:51 ` [PATCH rdma-next 3/4] RDMA/core: Make sure "ib_port" is valid when access sysfs node Leon Romanovsky
2022-11-07 8:51 ` [PATCH rdma-next 4/4] RDMA/nldev: Return "-EAGAIN" if the cm_id isn't from expected port Leon Romanovsky
2022-11-15 7:59 ` [PATCH rdma-next 0/4] Various core fixes Leon Romanovsky
2022-11-15 7:59 ` (subset) " 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.1667810736.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=markzhang@nvidia.com \
--cc=michaelgur@nvidia.com \
--cc=ohartoov@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.