From: Jorgen Hansen <jhansen@vmware.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
Pv-drivers <Pv-drivers@vmware.com>
Subject: Re: [PATCH] MAINTAINERS: Update for VMCI driver
Date: Wed, 21 Jul 2021 08:46:15 +0000 [thread overview]
Message-ID: <0C3493F7-AF29-417B-94EA-26871283E65A@vmware.com> (raw)
In-Reply-To: <YPan14jucU9/u6JL@kroah.com>
> On 20 Jul 2021, at 12:39, Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Jul 20, 2021 at 03:29:01AM -0700, Jorgen Hansen wrote:
>> Add maintainer info for the VMware VMCI driver.
>>
>> Signed-off-by: Jorgen Hansen <jhansen@vmware.com>
>> ---
>> MAINTAINERS | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index a61f4f3..7e7c6fa 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -19792,6 +19792,14 @@ L: netdev@vger.kernel.org
>> S: Supported
>> F: drivers/ptp/ptp_vmw.c
>>
>> +VMWARE VMCI DRIVER
>> +M: Jorgen Hansen <jhansen@vmware.com>
>> +M: Vishnu Dasa <vdasa@vmware.com>
>> +M: "VMware, Inc." <pv-drivers@vmware.com>
>
> Please do not use generic aliases as they provide no personal
> responsibility. Just stick with real people.
That makes sense. However, the pv-drivers list is used for keeping managers
and people helping with testing in the loop. So would adding pv-drivers as a
second L: entry be OK?
Thanks,
Jorgen
next prev parent reply other threads:[~2021-07-21 9:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 10:29 [PATCH] MAINTAINERS: Update for VMCI driver Jorgen Hansen
2021-07-20 10:39 ` Greg KH
[not found] ` <0DE37084-185C-4144-AF9E-22EC044B0CB5@vmware.com>
2021-07-20 18:11 ` Greg KH
2021-07-21 8:46 ` Jorgen Hansen [this message]
2021-07-21 9:00 ` Greg KH
2021-07-21 9:26 ` Jorgen Hansen
2021-07-21 9:33 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2021-07-20 10:25 Jorgen Hansen
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=0C3493F7-AF29-417B-94EA-26871283E65A@vmware.com \
--to=jhansen@vmware.com \
--cc=Pv-drivers@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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).