linux-kernel - Re: [PATCH] MAINTAINERS: Update for VMCI driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 21 Jul 2021 09:26:15 +0000
From:   Jorgen Hansen <jhansen@...are.com>
To:     Greg KH <gregkh@...uxfoundation.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "virtualization@...ts.linux-foundation.org" 
        <virtualization@...ts.linux-foundation.org>,
        Pv-drivers <Pv-drivers@...are.com>
Subject: Re: [PATCH] MAINTAINERS: Update for VMCI driver



> On 21 Jul 2021, at 11:00, Greg KH <gregkh@...uxfoundation.org> wrote:
> 
> On Wed, Jul 21, 2021 at 08:46:15AM +0000, Jorgen Hansen wrote:
>> 
>> 
>>> On 20 Jul 2021, at 12:39, Greg KH <gregkh@...uxfoundation.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@...are.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@...r.kernel.org
>>>> S:	Supported
>>>> F:	drivers/ptp/ptp_vmw.c
>>>> 
>>>> +VMWARE VMCI DRIVER
>>>> +M:	Jorgen Hansen <jhansen@...are.com>
>>>> +M:	Vishnu Dasa <vdasa@...are.com>
>>>> +M:	"VMware, Inc." <pv-drivers@...are.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?
> 
> Is it really a list?  If not, then that would not make much sense.

It is - with VMware subscribers only but anyone can post to it. If the intent of the
L: entries is to allow folks to subscribe to relevant information, then it isn’t
appropriate.

All existing vmw driver maintainer entries have pv-drivers as an M: entry,
so has there been a change in policy regarding this? The approach has
been quite useful for us.