From: Fam Zheng <famz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] qemu-options: Mention locking option of file driver
Date: Fri, 24 Nov 2017 16:44:29 +0800 [thread overview]
Message-ID: <20171124084429.GF3108@lemon> (raw)
In-Reply-To: <20171123170323.GC4375@localhost.localdomain>
On Thu, 11/23 18:03, Kevin Wolf wrote:
> Am 23.11.2017 um 14:59 hat Fam Zheng geschrieben:
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> > qemu-options.hx | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/qemu-options.hx b/qemu-options.hx
> > index 3728e9b4dd..bcb7a88ec3 100644
> > --- a/qemu-options.hx
> > +++ b/qemu-options.hx
> > @@ -693,6 +693,9 @@ This is the protocol-level block driver for accessing regular files.
> > The path to the image file in the local filesystem
> > @item aio
> > Specifies the AIO backend (threads/native, default: threads)
> > +@item locking
> > +Specifies whether the image file is protected with Linux OFD / POSIX locks.
> > +(auto/on/off, default: auto)
>
> Maybe "should be protected" would be better than "is protected"?
Yes.
>
> Do we want to explain what "auto" means?
Will add that.
Fam
prev parent reply other threads:[~2017-11-24 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 13:59 [Qemu-devel] [PATCH 0/2] docs: Add documentation for image locking Fam Zheng
2017-11-23 13:59 ` [Qemu-devel] [PATCH 1/2] docs: Add image locking subsection Fam Zheng
2017-11-23 16:07 ` Philipp Hahn
2017-11-24 8:43 ` Fam Zheng
2017-11-23 17:01 ` Kevin Wolf
2017-11-24 8:43 ` Fam Zheng
2017-11-23 13:59 ` [Qemu-devel] [PATCH 2/2] qemu-options: Mention locking option of file driver Fam Zheng
2017-11-23 17:03 ` Kevin Wolf
2017-11-24 8:44 ` Fam Zheng [this message]
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=20171124084429.GF3108@lemon \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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).