From: John Snow <jsnow@redhat.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
keith.busch@intel.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 1/2] nvme: Update header to include SGL related macros and members
Date: Mon, 26 Jun 2017 16:50:42 -0400 [thread overview]
Message-ID: <75d80dc9-377d-62fa-0c95-df2ae73039ca@redhat.com> (raw)
In-Reply-To: <20170606073806.8180-1-quwenruo@cn.fujitsu.com>
It looks like this patch hasn't gotten any attention in about a month. I
assume it's dead based on pending implementation that would actually
utilize these bits?
i.e., we don't need to check this patch in until the feature is actually
implemented, is that correct?
--js
On 06/06/2017 03:38 AM, Qu Wenruo wrote:
> Update nvme header to catch up with kernel.
> Most of the newly added members are from 1.2 and 1.3 spec, while the
> status code is only kept the same with kernel (around 1.1 spec).
>
> The major update is to add Scatter Gather List related macros and
> members, for later SGL support implementation.
>
> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
> ---
> hw/block/nvme.c | 16 ++++----
> hw/block/nvme.h | 122 +++++++++++++++++++++++++++++++++++++++++++++++---------
> 2 files changed, 111 insertions(+), 27 deletions(-)
>
[snip]
next prev parent reply other threads:[~2017-06-26 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 7:38 [Qemu-devel] [PATCH 1/2] nvme: Update header to include SGL related macros and members Qu Wenruo
2017-06-06 7:38 ` [Qemu-devel] [PATCH 2/2] nvme: Check PSDT flag for admin and rw command Qu Wenruo
2017-08-21 13:07 ` Christoph Hellwig
2017-06-26 20:50 ` John Snow [this message]
2017-08-21 13:06 ` [Qemu-devel] [PATCH 1/2] nvme: Update header to include SGL related macros and members Christoph Hellwig
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=75d80dc9-377d-62fa-0c95-df2ae73039ca@redhat.com \
--to=jsnow@redhat.com \
--cc=keith.busch@intel.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quwenruo@cn.fujitsu.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).