All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: virtio-fs@redhat.com
Subject: [Virtio-fs] Upstreaming virtiofsd
Date: Mon, 21 Oct 2019 16:04:14 +0100	[thread overview]
Message-ID: <20191021150414.GD5837@work-vm> (raw)

Hi,
  I've started upstreaming virtiofsd to qemu's contrib directory;
my first set (
https://lists.gnu.org/archive/html/qemu-devel/2019-10/msg05200.html )
is a minimal base set of patches that mounts and basically works - it
has none of the security work, the performance or many of the fixes.

In parallel with responding to any comments on that set, I'll be
working up the security set to be sent next; then performance and then
fixes.

Note, some of the patches that many of you have sent have been squashed
into other patches; I've kept a signed off (with something like 'fixes
from' or similar).  Many of the patches have been reformatted a bit.

Dave

--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK


             reply	other threads:[~2019-10-21 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 15:04 Dr. David Alan Gilbert [this message]
2019-10-22 15:56 ` [Virtio-fs] Upstreaming virtiofsd Stefan Hajnoczi
2019-10-23  9:58   ` Dr. David Alan Gilbert

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=20191021150414.GD5837@work-vm \
    --to=dgilbert@redhat.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.