From: Connor Kuehl <ckuehl@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Brijesh Singh <brijesh.singh@amd.com>,
qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [PATCH] Add Connor Kuehl as reviewer for AMD SEV
Date: Tue, 8 Jun 2021 15:46:52 -0500 [thread overview]
Message-ID: <4a9a1fb2-0be2-a8df-c3cd-7db6619ff729@redhat.com> (raw)
In-Reply-To: <YL/GNQUr4g3dyOQC@work-vm>
On 6/8/21 2:34 PM, Dr. David Alan Gilbert wrote:
>> Note: because there's no maintainer entry, when running
>> ./scripts/get_maintainers.pl on target/i386/sev.c, my name and the qemu
>> mailing list is the only thing that shows up... it doesn't even show
>> previous committers (as it would before applying this patch). Which is
>> probably not great considering I do not make pull requests to QEMU.
>>
>> Is the way forward to get someone to sign up as a maintainer before
>> applying a patch like this?
>
> If you wanted to do a submaintainer for it and send it to one of the x86
> maintainers rather than having to do full pulls?
I'm not opposed to this. I think I have a few of the right people on CC,
so let's see if they weigh in on this. Unless it means I have to manage
a GPG key again... (just kidding, kind of...)
Connor
next prev parent reply other threads:[~2021-06-08 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 19:25 [PATCH] Add Connor Kuehl as reviewer for AMD SEV Connor Kuehl
2021-06-08 19:28 ` Connor Kuehl
2021-06-08 19:34 ` Dr. David Alan Gilbert
2021-06-08 20:46 ` Connor Kuehl [this message]
2021-06-08 20:10 ` Daniel P. Berrangé
2021-06-08 20:32 ` Connor Kuehl
2021-06-08 20:45 ` Daniel P. Berrangé
2021-06-08 20:50 ` Connor Kuehl
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=4a9a1fb2-0be2-a8df-c3cd-7db6619ff729@redhat.com \
--to=ckuehl@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas.lendacky@amd.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 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.