From: John Snow <jsnow@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Kenneth Heitke <kenneth.heitke@intel.com>
Cc: kwolf@redhat.com, keith.busch@intel.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] nvme: add Get/Set Feature Timestamp support
Date: Mon, 13 May 2019 15:21:52 -0400 [thread overview]
Message-ID: <bcc74555-fe96-2859-db50-001a462ce4a7@redhat.com> (raw)
In-Reply-To: <20190409131903.GF16944@stefanha-x1.localdomain>
On 4/9/19 9:19 AM, Stefan Hajnoczi wrote:
> On Fri, Apr 05, 2019 at 03:41:17PM -0600, Kenneth Heitke wrote:
>> Signed-off-by: Kenneth Heitke <kenneth.heitke@intel.com>
>> ---
>> hw/block/nvme.c | 120 +++++++++++++++++++++++++++++++++++++++++-
>> hw/block/nvme.h | 3 ++
>> hw/block/trace-events | 2 +
>> include/block/nvme.h | 2 +
>> 4 files changed, 125 insertions(+), 2 deletions(-)
>
> CCing Maxim Levitsky <mlevitsk@redhat.com>, who is also working on NVMe
> emulation at the moment.
>
Did this patch stall? Do we still want it? Do we need reviewers?
next prev parent reply other threads:[~2019-05-13 19:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 21:41 [Qemu-devel] [PATCH] nvme: add Get/Set Feature Timestamp support Kenneth Heitke
2019-04-05 21:41 ` Kenneth Heitke
2019-04-09 13:19 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2019-04-09 13:19 ` Stefan Hajnoczi
2019-05-13 19:21 ` John Snow [this message]
2019-05-14 6:02 ` Klaus Birkelund
2019-05-16 23:24 ` Heitke, Kenneth
2019-05-17 5:35 ` Klaus Birkelund
2019-05-17 6:24 ` Klaus Birkelund
2019-05-17 17:08 ` Heitke, Kenneth
2019-05-18 1:49 ` Heitke, Kenneth
2019-05-18 7:30 ` Klaus Birkelund
2019-05-20 9:49 ` Kevin Wolf
2019-05-14 9:16 ` [Qemu-devel] " Philippe Mathieu-Daudé
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=bcc74555-fe96-2859-db50-001a462ce4a7@redhat.com \
--to=jsnow@redhat.com \
--cc=keith.busch@intel.com \
--cc=kenneth.heitke@intel.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).