From: Thomas Huth <thuth@redhat.com>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>, qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] configure: make clear that VirtFS is 9p
Date: Thu, 11 May 2023 17:51:57 +0200 [thread overview]
Message-ID: <7da3ca31-0faf-2c45-e34d-e45f2e93c906@redhat.com> (raw)
In-Reply-To: <E1px7Id-0000NE-OQ@lizzy.crudebyte.com>
On 11/05/2023 16.12, Christian Schoenebeck wrote:
> Add '9P' to the summary output section of 'VirtFS' to avoid being
> confused with virtiofs.
>
> Based-on: <20230503130757.863824-1-pefoley@google.com>
> Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> ---
> meson.build | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meson.build b/meson.build
> index 5d8373b608..5d65f53fec 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -3922,8 +3922,8 @@ if have_block
> summary_info += {'Block whitelist (rw)': get_option('block_drv_rw_whitelist')}
> summary_info += {'Block whitelist (ro)': get_option('block_drv_ro_whitelist')}
> summary_info += {'Use block whitelist in tools': get_option('block_drv_whitelist_in_tools')}
> - summary_info += {'VirtFS support': have_virtfs}
> - summary_info += {'VirtFS Proxy Helper support': have_virtfs_proxy_helper}
> + summary_info += {'VirtFS (9P) support': have_virtfs}
> + summary_info += {'VirtFS (9P) Proxy Helper support': have_virtfs_proxy_helper}
> summary_info += {'Live block migration': config_host_data.get('CONFIG_LIVE_BLOCK_MIGRATION')}
> summary_info += {'replication support': config_host_data.get('CONFIG_REPLICATION')}
> summary_info += {'bochs support': get_option('bochs').allowed()}
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2023-05-11 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 14:12 [PATCH] configure: make clear that VirtFS is 9p Christian Schoenebeck
2023-05-11 15:51 ` Thomas Huth [this message]
2023-05-13 16:29 ` Christian Schoenebeck
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=7da3ca31-0faf-2c45-e34d-e45f2e93c906@redhat.com \
--to=thuth@redhat.com \
--cc=groug@kaod.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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).