From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: zyjzyj2000@gmail.com, edwards@nvidia.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next 0/6] Misc cleanups and implement rereg_user_mr
Date: Fri, 9 Jun 2023 13:22:13 -0300 [thread overview]
Message-ID: <ZINRtUDu1J5Kh6hf@nvidia.com> (raw)
In-Reply-To: <20230530221334.89432-1-rpearsonhpe@gmail.com>
On Tue, May 30, 2023 at 05:13:29PM -0500, Bob Pearson wrote:
> This patch set does some preparatory cleanups and then implements the
> two simple cases of ib_rereg_user_mr.
>
> Bob Pearson (6):
> RDMA/rxe: Rename IB_ACCESS_REMOTE
> rdma/rxe: Optimize send path in rxe_resp.c
> RDMA/RXE: Fix access checks in rxe_check_bind_mw
> RDMA/RXE: Introduce rxe access supported flags
> RDMA/RXE: Let rkey == lkey for local access
> RDMA/RXE: Implement rereg_user_mr
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2023-06-09 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 22:13 [PATCH for-next 0/6] Misc cleanups and implement rereg_user_mr Bob Pearson
2023-05-30 22:13 ` [PATCH for-next 1/6] RDMA/rxe: Rename IB_ACCESS_REMOTE Bob Pearson
2023-05-30 22:13 ` [PATCH for-next 2/6] rdma/rxe: Optimize send path in rxe_resp.c Bob Pearson
2023-05-30 22:13 ` [PATCH for-next 3/6] RDMA/rxe: Fix access checks in rxe_check_bind_mw Bob Pearson
2023-05-30 22:13 ` [PATCH for-next 4/6] RDMA/rxe: Introduce rxe access supported flags Bob Pearson
2023-05-30 22:13 ` [PATCH for-next 5/6] RDMA/rxe: Let rkey == lkey for local access Bob Pearson
2023-05-30 22:13 ` [PATCH for-next 6/6] RDMA/rxe: Implement rereg_user_mr Bob Pearson
2023-06-09 16:22 ` Jason Gunthorpe [this message]
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=ZINRtUDu1J5Kh6hf@nvidia.com \
--to=jgg@nvidia.com \
--cc=edwards@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
--cc=zyjzyj2000@gmail.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).