From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Jon Doron <arilou@gmail.com>,
qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
Roman Kagan <rkagan@virtuozzo.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v4 0/1] hw/hyperv/vmbus: Is it maintained?
Date: Mon, 8 Nov 2021 08:30:59 +0100 [thread overview]
Message-ID: <96683e8d-9633-7cb8-98ab-0a8791e1c63e@redhat.com> (raw)
In-Reply-To: <e9c29f4d-d5d5-34aa-8311-7ad1fc05b7d6@oracle.com>
On 11/6/21 20:28, Maciej S. Szmigiero wrote:
> On 06.11.2021 14: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
>
> There's an email thread at [1] explaining the reasons for having VMBus
> infrastructure last time such question was asked.
>
> In short: mere presence of a working VMBus is needed for some high-speed
> Windows debugging, also people are working on VMBus host device drivers.
Great. Do you mind adding an entry in MAINTAINERS to
cover these files, so we stop wondering about them?
> Your patch makes sense to me, so for it:
> Reviewed-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com>
Thank you.
> [1]:
> https://lore.kernel.org/qemu-devel/20201009193919.GF7303@habkost.net/T/#u
>
next prev parent reply other threads:[~2021-11-08 7: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é [this message]
2021-11-13 15:23 ` Maciej S. Szmigiero
2021-11-12 18:32 ` Vladimir Sementsov-Ogievskiy
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=96683e8d-9633-7cb8-98ab-0a8791e1c63e@redhat.com \
--to=philmd@redhat.com \
--cc=arilou@gmail.com \
--cc=maciej.szmigiero@oracle.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=vsementsov@virtuozzo.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).