From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: Jon Doron <arilou@gmail.com>,
qemu-trivial@nongnu.org, Roman Kagan <rkagan@virtuozzo.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Maciej S . Szmigiero" <maciej.szmigiero@oracle.com>,
"Denis V. Lunev" <den@openvz.org>,
Roman Kagan <rvkagan@yandex-team.ru>
Subject: Re: [PATCH v4 0/1] hw/hyperv/vmbus: Is it maintained?
Date: Fri, 12 Nov 2021 21:32:31 +0300 [thread overview]
Message-ID: <54b75db4-8867-d1ee-e32c-bc3e4c23ec28@virtuozzo.com> (raw)
In-Reply-To: <20211106134155.582312-1-philmd@redhat.com>
Add Den and Roman (his new address)
06.11.2021 16:41, Philippe Mathieu-Daudé wrote:
> This is the 4th time I send this patch. Is the VMBus infrastructure
> used / maintained? Should we deprecate & remove?
>
> $ ./scripts/get_maintainer.pl -f hw/hyperv/vmbus.c -f include/hw/hyperv/vmbus.h
> get_maintainer.pl: No maintainers found
>
> Philippe Mathieu-Daudé (1):
> hw/hyperv/vmbus: Remove unused vmbus_load/save_req()
>
> include/hw/hyperv/vmbus.h | 3 --
> hw/hyperv/vmbus.c | 59 ---------------------------------------
> 2 files changed, 62 deletions(-)
>
--
Best regards,
Vladimir
next prev parent reply other threads:[~2021-11-12 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 13:41 [PATCH v4 0/1] hw/hyperv/vmbus: Is it maintained? Philippe Mathieu-Daudé
2021-11-06 13:41 ` [PATCH v4 1/1] hw/hyperv/vmbus: Remove unused vmbus_load/save_req() Philippe Mathieu-Daudé
2021-11-06 19:28 ` [PATCH v4 0/1] hw/hyperv/vmbus: Is it maintained? Maciej S. Szmigiero
2021-11-08 7:30 ` Philippe Mathieu-Daudé
2021-11-13 15:23 ` Maciej S. Szmigiero
2021-11-12 18:32 ` Vladimir Sementsov-Ogievskiy [this message]
2021-11-12 20:39 ` Roman Kagan
2021-11-13 15:23 ` Maciej S. Szmigiero
2021-11-16 10:05 ` Jon Doron
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=54b75db4-8867-d1ee-e32c-bc3e4c23ec28@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=arilou@gmail.com \
--cc=den@openvz.org \
--cc=maciej.szmigiero@oracle.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=rvkagan@yandex-team.ru \
/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).