From: Liu Zhenlong <dragonliu2018@gmail.com>
To: Md. Haris Iqbal <haris.iqbal@ionos.com>,
Jack Wang <jinpu.wang@ionos.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] RDMA/rtrs-clt: use find_next_zero_bit() for permit allocation
Date: Wed, 19 Aug 2026 01:22:36 +0800 [thread overview]
Message-ID: <178707375643.34993.16303244908977680572@gmail.com> (raw)
In-Reply-To: <20260818163513.53875-1-dragonliu2018@gmail.com>
Hi Jack,
Thanks for the review. Since I omitted the changelog in v2: the only
change from v1 is a simplified commit message; code unchanged, your
Reviewed-by carried.
Best,
Zhenlong
prev parent reply other threads:[~2026-08-18 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 16:59 [PATCH] RDMA/rtrs-clt: use find_next_zero_bit() for permit allocation Liu Zhenlong
2026-08-17 4:57 ` Jinpu Wang
2026-08-18 16:35 ` [PATCH v2] " Liu Zhenlong
2026-08-18 17:22 ` Liu Zhenlong [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=178707375643.34993.16303244908977680572@gmail.com \
--to=dragonliu2018@gmail.com \
--cc=haris.iqbal@ionos.com \
--cc=jgg@ziepe.ca \
--cc=jinpu.wang@ionos.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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).