From: Paolo Bonzini <pbonzini@redhat.com>
To: Maxim Levitsky <mlevitsk@redhat.com>, qemu-block@nongnu.org
Cc: Fam Zheng <fam@euphon.net>, Kevin Wolf <kwolf@redhat.com>,
Max Reitz <mreitz@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 4/5] block/nvme: add support for write zeros
Date: Tue, 16 Apr 2019 15:49:45 +0200 [thread overview]
Message-ID: <db949b72-40f1-137e-42a0-2682ff79f64b@redhat.com> (raw)
In-Reply-To: <20190415135746.7571-5-mlevitsk@redhat.com>
On 15/04/19 15:57, Maxim Levitsky wrote:
> +#define NVME_ID_NS_DLFEAT_READ_BEHAVIER(dlfeat) ((dlfeat) & 0x3)
> +#define NVME_ID_NS_DLFEAT_READ_BEHAVIER_UNDEFINED 0
> +#define NVME_ID_NS_DLFEAT_READ_BEHAVIER_ZEROS 1
> +#define NVME_ID_NS_DLFEAT_READ_BEHAVIER_ONES 2
> +
> +
s/BEHAVIER/BEHAVIOR/
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Maxim Levitsky <mlevitsk@redhat.com>, qemu-block@nongnu.org
Cc: Fam Zheng <fam@euphon.net>, Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 4/5] block/nvme: add support for write zeros
Date: Tue, 16 Apr 2019 15:49:45 +0200 [thread overview]
Message-ID: <db949b72-40f1-137e-42a0-2682ff79f64b@redhat.com> (raw)
Message-ID: <20190416134945.Aua0iwQ-VOw6UUxXYrSwSs1GzbmMiG3IRKcMBh0xwyw@z> (raw)
In-Reply-To: <20190415135746.7571-5-mlevitsk@redhat.com>
On 15/04/19 15:57, Maxim Levitsky wrote:
> +#define NVME_ID_NS_DLFEAT_READ_BEHAVIER(dlfeat) ((dlfeat) & 0x3)
> +#define NVME_ID_NS_DLFEAT_READ_BEHAVIER_UNDEFINED 0
> +#define NVME_ID_NS_DLFEAT_READ_BEHAVIER_ZEROS 1
> +#define NVME_ID_NS_DLFEAT_READ_BEHAVIER_ONES 2
> +
> +
s/BEHAVIER/BEHAVIOR/
Paolo
next prev parent reply other threads:[~2019-04-16 13:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 13:57 [Qemu-devel] [PATCH 0/5] Few fixes for userspace NVME driver Maxim Levitsky
2019-04-15 13:57 ` Maxim Levitsky
2019-04-15 13:57 ` [Qemu-devel] [PATCH 1/5] block/nvme: don't flip CQ phase bits Maxim Levitsky
2019-04-15 13:57 ` Maxim Levitsky
2019-04-15 13:57 ` [Qemu-devel] [PATCH 2/5] block/nvme: fix doorbell stride Maxim Levitsky
2019-04-15 13:57 ` Maxim Levitsky
2019-04-15 13:57 ` [Qemu-devel] [PATCH 3/5] block/nvme: support larger that 512 bytes sector devices Maxim Levitsky
2019-04-15 13:57 ` Maxim Levitsky
2019-04-15 13:57 ` [Qemu-devel] [PATCH 4/5] block/nvme: add support for write zeros Maxim Levitsky
2019-04-15 13:57 ` Maxim Levitsky
2019-04-16 13:49 ` Paolo Bonzini [this message]
2019-04-16 13:49 ` [Qemu-devel] [Qemu-block] " Paolo Bonzini
2019-04-15 13:57 ` [Qemu-devel] [PATCH 5/5] block/nvme: add support for discard Maxim Levitsky
2019-04-15 13:57 ` Maxim Levitsky
2019-04-16 13:50 ` [Qemu-devel] [Qemu-block] " Paolo Bonzini
2019-04-16 13:50 ` Paolo Bonzini
2019-04-16 13:50 ` [Qemu-devel] [Qemu-block] [PATCH 0/5] Few fixes for userspace NVME driver Paolo Bonzini
2019-04-16 13:50 ` Paolo Bonzini
2019-04-17 19:57 ` Maxim Levitsky
2019-04-17 19:57 ` Maxim Levitsky
2019-06-02 9:12 ` [Qemu-devel] " Maxim Levitsky
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=db949b72-40f1-137e-42a0-2682ff79f64b@redhat.com \
--to=pbonzini@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mlevitsk@redhat.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).