From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvmet-rdma: fix nvmet_rdma_rsp leak
Date: Thu, 30 Jun 2016 08:31:59 +0200 [thread overview]
Message-ID: <20160630063159.GA5191@lst.de> (raw)
In-Reply-To: <1467221797-2576-1-git-send-email-mlin@kernel.org>
Thanks a lot Ming,
this looks like the real root cause. Applied to nvmf-all.3.
next prev parent reply other threads:[~2016-06-30 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 17:36 [PATCH] nvmet-rdma: fix nvmet_rdma_rsp leak Ming Lin
2016-06-30 6:31 ` Christoph Hellwig [this message]
2016-07-13 10:12 ` Sagi Grimberg
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=20160630063159.GA5191@lst.de \
--to=hch@lst.de \
/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).