From: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
To: Leo Yan <leo.yan@linaro.org>, qemu-devel@nongnu.org
Cc: "Alex Benné e" <alex.bennee@linaro.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Leo Yan" <leo.yan@linaro.org>
Subject: Re: [PATCH v1 3/4] hw/virtio: Move vhost-user-input into virtio folder
Date: Mon, 13 Nov 2023 09:24:09 +0200 [thread overview]
Message-ID: <41wpa.smmzo0kr8q76@linaro.org> (raw)
In-Reply-To: <20231113011642.48176-4-leo.yan@linaro.org>
Hello Leo,
On Mon, 13 Nov 2023 03:16, Leo Yan <leo.yan@linaro.org> wrote:
>vhost-user-input is in the input folder. On the other hand, the folder
>'hw/virtio' maintains other virtio stubs (e.g. I2C, RNG, GPIO, etc).
>
>This patch moves vhost-user-input into the virtio folder for better code
>organization. No functionality change.
>
>Signed-off-by: Leo Yan <leo.yan@linaro.org>
Make sure MAINTAINERS is updated as well, it points to hw/input:
virtio-input
M: Gerd Hoffmann <kraxel@redhat.com>
S: Odd Fixes
F: hw/input/vhost-user-input.c
F: hw/input/virtio-input*.c
F: include/hw/virtio/virtio-input.h
F: contrib/vhost-user-input/*
next prev parent reply other threads:[~2023-11-13 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 1:16 [PATCH v1 0/4] virtio: Refactor vhost input stub Leo Yan
2023-11-13 1:16 ` [PATCH v1 1/4] hw/virtio: Support set_config() callback in vhost-user-base Leo Yan
2023-11-13 1:16 ` [PATCH v1 2/4] docs/system: Add vhost-user-input documentation Leo Yan
2023-11-13 1:33 ` Leo Yan
2023-11-13 1:16 ` [PATCH v1 3/4] hw/virtio: Move vhost-user-input into virtio folder Leo Yan
2023-11-13 7:24 ` Manos Pitsidianakis [this message]
2023-11-13 17:48 ` Leo Yan
2023-11-13 1:16 ` [PATCH v1 4/4] hw/virtio: derive vhost-user-input from vhost-user-base Leo Yan
2023-11-13 6:29 ` [PATCH v1 0/4] virtio: Refactor vhost input stub Michael S. Tsirkin
2023-11-13 19:05 ` Leo Yan
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=41wpa.smmzo0kr8q76@linaro.org \
--to=manos.pitsidianakis@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=kraxel@redhat.com \
--cc=leo.yan@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--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 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.