From: Christoph Hellwig <hch@infradead.org>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-nvme@lists.infradead.org, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: Re: [PATCH 2/2] nvmet-rdma: fix response resource leak on queue teardown
Date: Tue, 30 Jun 2026 04:54:55 -0700 [thread overview]
Message-ID: <akOuj5CTawdfxq1Y@infradead.org> (raw)
In-Reply-To: <20260629051529.810925-3-shinichiro.kawasaki@wdc.com>
Looks good;
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2026-06-30 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 5:15 [PATCH 0/2] nvmet-rdma: fix response resource leak on queue teardown Shin'ichiro Kawasaki
2026-06-29 5:15 ` [PATCH 1/2] nvmet-rdma: factor out response resource cleanup Shin'ichiro Kawasaki
2026-06-30 11:54 ` Christoph Hellwig
2026-06-29 5:15 ` [PATCH 2/2] nvmet-rdma: fix response resource leak on queue teardown Shin'ichiro Kawasaki
2026-06-30 11:54 ` Christoph Hellwig [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=akOuj5CTawdfxq1Y@infradead.org \
--to=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.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