From: Bin Meng <bin.meng@windriver.com>
To: Greg Kurz <groug@kaod.org>,
Christian Schoenebeck <qemu_oss@crudebyte.com>,
qemu-devel@nongnu.org
Cc: Guohuai Shi <guohuai.shi@windriver.com>
Subject: [PATCH v3 14/17] fsdev: Disable proxy fs driver on Windows
Date: Mon, 19 Dec 2022 18:20:18 +0800 [thread overview]
Message-ID: <20221219102022.2167736-15-bin.meng@windriver.com> (raw)
In-Reply-To: <20221219102022.2167736-1-bin.meng@windriver.com>
From: Guohuai Shi <guohuai.shi@windriver.com>
We don't plan to support 'proxy' file system driver for 9pfs on
Windows. Disable it for Windows build.
Signed-off-by: Guohuai Shi <guohuai.shi@windriver.com>
Signed-off-by: Bin Meng <bin.meng@windriver.com>
---
(no changes since v1)
fsdev/qemu-fsdev.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fsdev/qemu-fsdev.c b/fsdev/qemu-fsdev.c
index 3da64e9f72..58e0710fbb 100644
--- a/fsdev/qemu-fsdev.c
+++ b/fsdev/qemu-fsdev.c
@@ -89,6 +89,7 @@ static FsDriverTable FsDrivers[] = {
NULL
},
},
+#ifndef CONFIG_WIN32
{
.name = "proxy",
.ops = &proxy_ops,
@@ -100,6 +101,7 @@ static FsDriverTable FsDrivers[] = {
NULL
},
},
+#endif
};
static int validate_opt(void *opaque, const char *name, const char *value,
--
2.25.1
next prev parent reply other threads:[~2022-12-19 10:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 10:20 [PATCH v3 00/17] hw/9pfs: Add 9pfs support for Windows Bin Meng
2022-12-19 10:20 ` [PATCH v3 01/17] qemu/xattr.h: Exclude <sys/xattr.h> " Bin Meng
2022-12-19 10:20 ` [PATCH v3 02/17] hw/9pfs: Drop unnecessary *xattr wrapper API declarations Bin Meng
2022-12-19 10:20 ` [PATCH v3 03/17] hw/9pfs: Replace the direct call to xxxat() APIs with a wrapper Bin Meng
2022-12-19 10:20 ` [PATCH v3 04/17] hw/9pfs: Add missing definitions for Windows Bin Meng
2022-12-19 10:20 ` [PATCH v3 05/17] hw/9pfs: Implement Windows specific utilities functions for 9pfs Bin Meng
2022-12-19 10:20 ` [PATCH v3 06/17] hw/9pfs: Update the local fs driver to support Windows Bin Meng
2022-12-19 10:20 ` [PATCH v3 07/17] hw/9pfs: Support getting current directory offset for Windows Bin Meng
2022-12-21 14:48 ` Christian Schoenebeck
2022-12-21 18:02 ` Shi, Guohuai
2022-12-28 11:51 ` Christian Schoenebeck
2022-12-29 6:03 ` Shi, Guohuai
2022-12-30 13:36 ` Christian Schoenebeck
2022-12-19 10:20 ` [PATCH v3 08/17] hw/9pfs: update helper qemu_stat_rdev() Bin Meng
2022-12-19 10:20 ` [PATCH v3 09/17] hw/9pfs: Add a helper qemu_stat_blksize() Bin Meng
2022-12-19 10:20 ` [PATCH v3 10/17] hw/9pfs: Disable unsupported flags and features for Windows Bin Meng
2022-12-19 10:20 ` [PATCH v3 11/17] hw/9pfs: Update v9fs_set_fd_limit() " Bin Meng
2022-12-19 10:20 ` [PATCH v3 12/17] hw/9pfs: Add Linux error number definition Bin Meng
2022-12-19 10:20 ` [PATCH v3 13/17] hw/9pfs: Translate Windows errno to Linux value Bin Meng
2022-12-19 10:20 ` Bin Meng [this message]
2022-12-19 10:20 ` [PATCH v3 15/17] hw/9pfs: Update synth fs driver for Windows Bin Meng
2022-12-19 10:20 ` [PATCH v3 16/17] tests/qtest: virtio-9p-test: Adapt the case for win32 Bin Meng
2022-12-19 10:20 ` [PATCH v3 17/17] meson.build: Turn on virtfs for Windows Bin Meng
2022-12-21 14:14 ` [PATCH v3 00/17] hw/9pfs: Add 9pfs support " 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=20221219102022.2167736-15-bin.meng@windriver.com \
--to=bin.meng@windriver.com \
--cc=groug@kaod.org \
--cc=guohuai.shi@windriver.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).