From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Leon Romanovsky <leon@kernel.org>
Cc: Li Zhijian <lizhijian@fujitsu.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
zyjzyj2000@gmail.com, jgg@ziepe.ca,
Daisuke Matsuda <dskmtsd@gmail.com>
Subject: Re: [PATCH] IB/rxe: ODP: Fix missing umem_odp->umem_mutex unlock
Date: Tue, 30 Dec 2025 07:24:49 -0800 [thread overview]
Message-ID: <fa30ffed-a048-4ddd-8c2b-c12da46dabe5@linux.dev> (raw)
In-Reply-To: <20251230092751.GA27868@unreal>
在 2025/12/30 1:27, Leon Romanovsky 写道:
> I made a few adjustments to the commit message, added a Fixes tag, included
> your Reviewed-by, and applied the patch.
Thanks a lot.
Zhu Yanjun
>
>
>
--
Best Regards,
Yanjun.Zhu
next prev parent reply other threads:[~2025-12-30 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 9:41 [PATCH] IB/rxe: ODP: Fix missing umem_odp->umem_mutex unlock Li Zhijian
2025-12-27 1:05 ` Zhu Yanjun
2025-12-30 9:27 ` Leon Romanovsky
2025-12-30 15:24 ` Zhu Yanjun [this message]
2025-12-30 9:28 ` 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=fa30ffed-a048-4ddd-8c2b-c12da46dabe5@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=dskmtsd@gmail.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.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).