From: Kevin Wolf <kwolf@redhat.com>
To: Li Qiang <liq3ea@gmail.com>
Cc: keith.busch@intel.com, mreitz@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] nvme: fix two issues in nvme unhotplug
Date: Wed, 7 Nov 2018 10:54:52 +0100 [thread overview]
Message-ID: <20181107095452.GA4721@linux.fritz.box> (raw)
In-Reply-To: <1540794581-33578-1-git-send-email-liq3ea@gmail.com>
Am 29.10.2018 um 07:29 hat Li Qiang geschrieben:
> The first corrent the refcount and second fix a memory leak.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2018-11-07 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 6:29 [Qemu-devel] [PATCH 0/2] nvme: fix two issues in nvme unhotplug Li Qiang
2018-10-29 6:29 ` [Qemu-devel] [PATCH 1/2] nvme: don't unref ctrl_mem when device unrealized Li Qiang
2018-11-05 14:57 ` Li Qiang
2018-11-06 15:58 ` Igor Mammedov
2018-10-29 6:29 ` [Qemu-devel] [PATCH 2/2] nvme: free cmbuf in nvme_exit Li Qiang
2018-10-29 12:32 ` Philippe Mathieu-Daudé
2018-11-07 9:54 ` Kevin Wolf [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=20181107095452.GA4721@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=keith.busch@intel.com \
--cc=liq3ea@gmail.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).