From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: Li Qiang <liq3ea@gmail.com>, qemu-devel@nongnu.org
Cc: Li Qiang <liqiang6-s@360.cn>
Subject: Re: [Qemu-devel] [PATCH] nvdimm: allow read/write zero-size namespace label
Date: Fri, 13 Jan 2017 17:00:31 +0800 [thread overview]
Message-ID: <011014c2-1129-cd48-f13d-66d7951d3e3c@linux.intel.com> (raw)
In-Reply-To: <5878435d.54b31c0a.39a7b.4e93@mx.google.com>
On 01/13/2017 11:02 AM, Li Qiang wrote:
> From: Li Qiang <liqiang6-s@360.cn>
>
> The spec doesn't say the namespace label can't be zero
> when read/write it. As this is no harmful, just allow
> it.
>
WHY?
The spec said that the label should be at least 128K.
next prev parent reply other threads:[~2017-01-13 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 3:02 [Qemu-devel] [PATCH] nvdimm: allow read/write zero-size namespace label Li Qiang
2017-01-13 9:00 ` Xiao Guangrong [this message]
2017-01-14 11:22 ` Li Qiang
2017-01-16 13:34 ` Stefan Hajnoczi
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=011014c2-1129-cd48-f13d-66d7951d3e3c@linux.intel.com \
--to=guangrong.xiao@linux.intel.com \
--cc=liq3ea@gmail.com \
--cc=liqiang6-s@360.cn \
--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).