From: Kevin Wolf <kwolf@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <keith.busch@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] NVMe volatile write cache fixes
Date: Wed, 17 Jun 2015 14:24:06 +0200 [thread overview]
Message-ID: <20150617122406.GE4202@noname.str.redhat.com> (raw)
In-Reply-To: <20150617115924.GA10087@lst.de>
Am 17.06.2015 um 13:59 hat Christoph Hellwig geschrieben:
> Thank Eric.
>
> Kevin,
>
> do you want me to resend the series with these cover letter/cc fixes or
> is it okay this time?
It's not worth a respin. I'm just waiting for an Acked-by (or whatever
other outcome of a review) from Keith before I merge this.
Kevin
next prev parent reply other threads:[~2015-06-17 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1434016899-18643-1-git-send-email-hch@lst.de>
2015-06-11 12:26 ` [Qemu-devel] [Qemu-block] NVMe volatile write cache fixes Eric Blake
2015-06-17 11:59 ` Christoph Hellwig
2015-06-17 12:24 ` Kevin Wolf [this message]
2015-07-04 4:58 ` Christoph Hellwig
2015-07-08 10:05 ` Kevin Wolf
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=20150617122406.GE4202@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=hch@lst.de \
--cc=keith.busch@intel.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).