From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Keith Busch <keith.busch@intel.com>,
Christoph Hellwig <hch@lst.de>,
qemu-block@nongnu.org,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] NVMe volatile write cache fixes
Date: Sat, 4 Jul 2015 06:58:43 +0200 [thread overview]
Message-ID: <20150704045843.GA31893@lst.de> (raw)
In-Reply-To: <20150617122406.GE4202@noname.str.redhat.com>
On Wed, Jun 17, 2015 at 02:24:06PM +0200, Kevin Wolf wrote:
> 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.
Given that you got the Ack a while ago is there any chance to get this data
integrity fix in before qemu 2.4?
next prev parent reply other threads:[~2015-07-04 4:58 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
2015-07-04 4:58 ` Christoph Hellwig [this message]
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=20150704045843.GA31893@lst.de \
--to=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=kwolf@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).