From: Stefano Garzarella <sgarzare@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
integration@gluster.org, qemu-block@nongnu.org,
Markus Armbruster <armbru@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/3] Update documentation and help related to the preallocation parameter
Date: Fri, 24 May 2019 09:58:45 +0200 [thread overview]
Message-ID: <20190524075848.23781-1-sgarzare@redhat.com> (raw)
Following Markus' advice, I updated the documentation of preallocation
parameter in qapi/block-core.json adding default and allowed values (patch 1).
I also updated the help related to BLOCK_OPT_PREALLOC in the QemuOptsList of
file-posix (patch 2) and gluster (patch 3).
v2:
- Patch 1: removed references to "file-win32" and "file-posix" in the
block comment [Markus]
- Patch 3: reworded commit message [Markus]
Stefano Garzarella (3):
qapi/block-core: update documentation of preallocation parameter
block/file-posix: update .help of BLOCK_OPT_PREALLOC option
block/gluster: update .help of BLOCK_OPT_PREALLOC option
qapi/block-core.json | 20 ++++++++++++++------
block/file-posix.c | 6 +++++-
block/gluster.c | 9 ++++++++-
3 files changed, 27 insertions(+), 8 deletions(-)
--
2.20.1
next reply other threads:[~2019-05-24 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 7:58 Stefano Garzarella [this message]
2019-05-24 7:58 ` [Qemu-devel] [PATCH v2 1/3] qapi/block-core: update documentation of preallocation parameter Stefano Garzarella
2019-05-24 7:58 ` [Qemu-devel] [PATCH v2 2/3] block/file-posix: update .help of BLOCK_OPT_PREALLOC option Stefano Garzarella
2019-05-24 7:58 ` [Qemu-devel] [PATCH v2 3/3] block/gluster: " Stefano Garzarella
2019-05-28 6:15 ` [Qemu-devel] [PATCH v2 0/3] Update documentation and help related to the preallocation parameter Markus Armbruster
2019-05-29 12:49 ` Max Reitz
2019-05-29 14:14 ` Markus Armbruster
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=20190524075848.23781-1-sgarzare@redhat.com \
--to=sgarzare@redhat.com \
--cc=armbru@redhat.com \
--cc=integration@gluster.org \
--cc=kwolf@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).