From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Greg Kurz <groug@kaod.org>, Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Wilfred Mallawa <wilfred.mallawa@wdc.com>
Subject: Re: [PATCH] MAINTAINERS: Add 9p test client to section "virtio-9p"
Date: Wed, 30 Nov 2022 19:12:42 +0100 [thread overview]
Message-ID: <4272112.8SkojGVNeE@silver> (raw)
In-Reply-To: <E1ozhlV-0007BU-0g@lizzy.crudebyte.com>
On Monday, November 28, 2022 6:12:04 PM CET Christian Schoenebeck wrote:
> The 9p test cases use a dedicated, lite-weight 9p client implementation
> (using virtio transport) under tests/qtest/libqos/ to communicate with
> QEMU's 9p server.
>
> It's already there for a long time. Let's officially assign it to 9p
> maintainers.
>
> Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> ---
Queued on 9p.next:
https://github.com/cschoenebeck/qemu/commits/9p.next
Thanks!
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index cf24910249..4f156a99f1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2036,6 +2036,7 @@ X: hw/9pfs/xen-9p*
> F: fsdev/
> F: docs/tools/virtfs-proxy-helper.rst
> F: tests/qtest/virtio-9p-test.c
> +F: tests/qtest/libqos/virtio-9p*
> T: git https://gitlab.com/gkurz/qemu.git 9p-next
> T: git https://github.com/cschoenebeck/qemu.git 9p.next
>
>
prev parent reply other threads:[~2022-11-30 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 17:12 [PATCH] MAINTAINERS: Add 9p test client to section "virtio-9p" Christian Schoenebeck
2022-11-28 18:07 ` Philippe Mathieu-Daudé
2022-11-29 6:35 ` Greg Kurz
2022-11-29 7:01 ` Wilfred Mallawa
2022-11-30 18:12 ` Christian Schoenebeck [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=4272112.8SkojGVNeE@silver \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wilfred.mallawa@wdc.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).