From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] qsd: Document FUSE exports
Date: Mon, 29 Mar 2021 18:29:04 +0200 [thread overview]
Message-ID: <33af8c29-9acd-9822-4fd4-4212f8b8b3bf@redhat.com> (raw)
In-Reply-To: <20210217115844.62661-1-mreitz@redhat.com>
On 17.02.21 12:58, Max Reitz wrote:
> Implementing FUSE exports required no changes to the storage daemon, so
> we forgot to document them there. Considering that both NBD and
> vhost-user-blk exports are documented in its man page (and NBD exports
> in its --help text), we should probably do the same for FUSE.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> docs/tools/qemu-storage-daemon.rst | 19 +++++++++++++++++++
> storage-daemon/qemu-storage-daemon.c | 4 ++++
> 2 files changed, 23 insertions(+)
Thanks for the review, applied to my block branch:
https://git.xanclic.moe/XanClic/qemu/commits/branch/block
Max
prev parent reply other threads:[~2021-03-29 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 11:58 [PATCH] qsd: Document FUSE exports Max Reitz
2021-02-17 16:26 ` Eric Blake
2021-02-18 8:49 ` Max Reitz
2021-03-29 16:29 ` Max Reitz [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=33af8c29-9acd-9822-4fd4-4212f8b8b3bf@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@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).