All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>
Cc: "virtio-fs@redhat.com" <virtio-fs@redhat.com>
Subject: Re: [Virtio-fs] Changes in -dev branch
Date: Tue, 14 Jan 2020 12:25:42 +0000	[thread overview]
Message-ID: <20200114122542.GH2812@work-vm> (raw)
In-Reply-To: <4dcf854ab5133f4bc77191bd3f49aa8e9a96c57d.camel@intel.com>

* Boeuf, Sebastien (sebastien.boeuf@intel.com) wrote:
> Hi Dave,
> 
> On Fri, 2020-01-10 at 19:03 +0000, Dr. David Alan Gilbert wrote:
> > Hi,
> >    I've just pushed a new version of the virtio-fs-dev branch in
> >  https://gitlab.com/virtio-fs/qemu
> >  
> > some things to note:
> > 
> >   a) The old '-o vhost_user_socket' syntax has now been replaced
> >      by the syntax matching qemu's standardised vhost-user interface
> >      which is;
> > 
> >      ./virtiofsd --socket-path=/path/whereever
> 
> I was expecting that "./virtiofsd --socket-path /path/whereever" would
> work too, but it doesn't. Is this the expected behavior?
> 
> Just asking cause it feels weird that we must add "=" here.

--socket-path= is the stadnard defined in qemu's
docs/interop/vhost-user.rst and fuse_lowlevel also seems
to standardise on options that take parameters using =.

Dave

> Thanks,
> Sebastien
> 
> > 
> >   b) It's got about 64 of the main patches reviewed by Daniel
> > Berrangé
> >      - about another 40 that need reviewing; please leap in
> >      and review any patches on the qemu-devel thread for any patches
> >      that are missing reviews.
> > 
> >   c) The set that I've just pushed has fixes for all the things
> >      Daniel spotted; so there's a bunch of mostly minor changes.
> > 
> >   d) It's also got patches that were received on list since
> >      mid December.
> > 
> > Dave
> > 
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> > 
> > _______________________________________________
> > Virtio-fs mailing list
> > Virtio-fs@redhat.com
> > https://www.redhat.com/mailman/listinfo/virtio-fs
> > 
> ---------------------------------------------------------------------
> Intel Corporation SAS (French simplified joint stock company)
> Registered headquarters: "Les Montalets"- 2, rue de Paris, 
> 92196 Meudon Cedex, France
> Registration Number:  302 456 199 R.C.S. NANTERRE
> Capital: 4,572,000 Euros
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK


  reply	other threads:[~2020-01-14 12:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 19:03 [Virtio-fs] Changes in -dev branch Dr. David Alan Gilbert
2020-01-13  7:55 ` Boeuf, Sebastien
2020-01-14 12:25   ` Dr. David Alan Gilbert [this message]
2020-01-15  7:34     ` Boeuf, Sebastien
  -- strict thread matches above, loose matches on Subject: below --
2020-10-28 19:00 Dr. David Alan Gilbert
2020-09-23 12:28 Dr. David Alan Gilbert
2019-12-11 12:16 Dr. David Alan Gilbert
2019-12-11 12:41 ` Boeuf, Sebastien
2019-12-11 14:00   ` Dr. David Alan Gilbert
2019-12-11 17:16     ` Boeuf, Sebastien

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=20200114122542.GH2812@work-vm \
    --to=dgilbert@redhat.com \
    --cc=sebastien.boeuf@intel.com \
    --cc=virtio-fs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.