From: Thomas Huth <thuth@redhat.com>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>,
Richard Henderson <richard.henderson@linaro.org>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH][RESEND] MAINTAINERS: Add myself as a reviewer for Hyper-V VMBus
Date: Tue, 10 May 2022 08:31:23 +0200 [thread overview]
Message-ID: <4e03945d-fb92-494d-53a8-f22ee91501c9@redhat.com> (raw)
In-Reply-To: <6ed59ef8-53bc-74ba-432c-955ad72d9f23@maciej.szmigiero.name>
On 09/05/2022 19.59, Maciej S. Szmigiero wrote:
> On 6.05.2022 07:31, Thomas Huth wrote:
>> On 05/05/2022 21.36, Maciej S. Szmigiero wrote:
>>> From: "Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>
>>>
>>> This way there is at least some contact point for incoming patches.
>>>
>>> We'll see whether the code still gets just a random patch a few times
>>> a year or whether it requires a permanent maintainer to take care of it.
>>>
>>> Signed-off-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com>
>>> ---
>>> Resending, since the previous submission at [1] wasn't picked up.
>>> [1]:
>>> https://lore.kernel.org/qemu-devel/b145dcf08ae606e9d29e55b2f701a3fe4f16b347.1637433881.git.maciej.szmigiero@oracle.com/
>>>
>>>
>>> MAINTAINERS | 6 ++++++
>>> 1 file changed, 6 insertions(+)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 218c9459b6..907f1d4a88 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -1776,6 +1776,12 @@ F: include/hw/block/fdc.h
>>> F: tests/qtest/fdc-test.c
>>> T: git https://gitlab.com/jsnow/qemu.git ide
>>> +Hyper-V VMBus
>>> +S: Odd Fixes
>>> +R: Maciej S. Szmigiero <maciej.szmigiero@oracle.com>
>>> +F: hw/hyperv/vmbus.c
>>> +F: include/hw/hyperv/vmbus*.h
>>
>> If there's no dedicated maintainer, I'd rather pick "Orphan" instead of
>> "Odd Fixes" here?
>> Who's supposed to pick up the related patches?
>
> I think I can do this, as long as I know who to send pull requests to
> and on what schedule.
Pull requests are sent via mail to the qemu-devel mailing list, see
https://www.qemu.org/docs/master/devel/submitting-a-pull-request.html for
some details. During the normal development phase, pull requests can be sent
as necessary for new patches. Just during the freeze period (the next one
will be announced on https://wiki.qemu.org/Planning/7.1 later), only bug
fixes (no new feature) should be sent.
Thomas
prev parent reply other threads:[~2022-05-10 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 19:36 [PATCH][RESEND] MAINTAINERS: Add myself as a reviewer for Hyper-V VMBus Maciej S. Szmigiero
2022-05-06 5:31 ` Thomas Huth
2022-05-09 17:59 ` Maciej S. Szmigiero
2022-05-10 6:31 ` Thomas Huth [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=4e03945d-fb92-494d-53a8-f22ee91501c9@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=mail@maciej.szmigiero.name \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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).