qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtfs: Add missing "id" parameter in documentation
Date: Mon, 6 May 2019 08:07:12 +0200	[thread overview]
Message-ID: <20190506080712.2fc846d0@bahia.lan> (raw)
In-Reply-To: <3189f4fe-d712-5903-8c42-97d72ddb4131@redhat.com>

On Mon, 6 May 2019 05:49:40 +0200
Thomas Huth <thuth@redhat.com> wrote:

> On 05/05/2019 20.32, Greg Kurz wrote:
> > Hi Thomas,
> > 
> > Thanks for the janitoring :)
> > 
> > On Sun,  5 May 2019 16:45:27 +0200
> > Thomas Huth <thuth@redhat.com> wrote:
> >   
> >> ... and remove the square brackets from "path" and "security_model",
> >> since these parameters are not optional.
> >>  
> > 
> > Well this is only true when fsdriver == local, but the other fs drivers,
> > ie. proxy and synth, don't need it at all.  
> 
> Ok, then this is wrong in the output of "--help" instead.
> 

Yeah, I've taken a look and both the usage and the man page need
fixing...

> > Each driver has its own set of
> > options actually. This should better be described with separate lines IMHO.
> > 
> > Also, it should be stated that "id" relates to the fs backend, ie. it
> > belongs to the -fsdev "id" space, not to the device that gets exposed
> > to the guest.  
> 
> Hmm, maybe it would be better if you do this patch, since you've
> definitely got way more knowledge here than I do... Otherwise, I can
> have a try, but it might take a while till I get back to this...
> 

Sure, I'll do that.

>  Thomas

Cheers,

--
Greg


      reply	other threads:[~2019-05-06  6:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-05 14:45 [Qemu-devel] [PATCH] virtfs: Add missing "id" parameter in documentation Thomas Huth
2019-05-05 14:45 ` Thomas Huth
2019-05-05 18:32 ` Greg Kurz
2019-05-05 18:32   ` Greg Kurz
2019-05-06  3:49   ` Thomas Huth
2019-05-06  6:07     ` Greg Kurz [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=20190506080712.2fc846d0@bahia.lan \
    --to=groug@kaod.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.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).