From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 99710C433EF for ; Tue, 9 Nov 2021 00:22:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 76FB461107 for ; Tue, 9 Nov 2021 00:22:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235565AbhKIAZH (ORCPT ); Mon, 8 Nov 2021 19:25:07 -0500 Received: from outgoing-stata.csail.mit.edu ([128.30.2.210]:53053 "EHLO outgoing-stata.csail.mit.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231793AbhKIAZH (ORCPT ); Mon, 8 Nov 2021 19:25:07 -0500 Received: from c-24-16-8-193.hsd1.wa.comcast.net ([24.16.8.193] helo=srivatsab-a02.vmware.com) by outgoing-stata.csail.mit.edu with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1mkEu2-000R2P-5t; Mon, 08 Nov 2021 19:22:18 -0500 To: Joe Perches , jgross@suse.com, x86@kernel.org, pv-drivers@vmware.com Cc: Nadav Amit , Vivek Thampi , Vishal Bhakta , Ronak Doshi , linux-graphics-maintainer@vmware.com, dri-devel@lists.freedesktop.org, linux-rdma@vger.kernel.org, linux-scsi@vger.kernel.org, netdev@vger.kernel.org, linux-input@vger.kernel.org, Zack Rusin , sdeep@vmware.com, amakhalov@vmware.com, virtualization@lists.linux-foundation.org, keerthanak@vmware.com, srivatsab@vmware.com, anishs@vmware.com, linux-kernel@vger.kernel.org, Thomas Gleixner , gregkh@linuxfoundation.org References: <163640336232.62866.489924062999332446.stgit@srivatsa-dev> <163640339370.62866.3435211389009241865.stgit@srivatsa-dev> <5179a7c097e0bb88f95642a394f53c53e64b66b1.camel@perches.com> From: "Srivatsa S. Bhat" Subject: Re: [PATCH 2/2] MAINTAINERS: Mark VMware mailing list entries as private Message-ID: Date: Mon, 8 Nov 2021 16:22:14 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: <5179a7c097e0bb88f95642a394f53c53e64b66b1.camel@perches.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-input@vger.kernel.org +Greg, Thomas Hi Joe, On 11/8/21 3:37 PM, Joe Perches wrote: > On Mon, 2021-11-08 at 12:30 -0800, Srivatsa S. Bhat wrote: >> From: Srivatsa S. Bhat (VMware) >> >> VMware mailing lists in the MAINTAINERS file are private lists meant >> for VMware-internal review/notification for patches to the respective >> subsystems. So, in an earlier discussion [1][2], it was recommended to >> mark them as such. Update all the remaining VMware mailing list >> references to use that format -- "L: list@address (private)". > [] >> diff --git a/MAINTAINERS b/MAINTAINERS > [] >> @@ -6134,8 +6134,8 @@ T: git git://anongit.freedesktop.org/drm/drm-misc >> F: drivers/gpu/drm/vboxvideo/ >> >> DRM DRIVER FOR VMWARE VIRTUAL GPU >> -M: "VMware Graphics" >> M: Zack Rusin >> +L: linux-graphics-maintainer@vmware.com (private) > > This MAINTAINERS file is for _public_ use, marking something > non-public isn't useful. > > private makes no sense and likely these L: entries shouldn't exist. > > Well, the public can send messages to this list, but membership is restricted. In many ways, I believe this is similar to x86@kernel.org, which is an email alias that anyone can post to in order to reach the x86 maintainer community for patch review. I see x86@kernel.org listed as both L: and M: in the MAINTAINERS file, among different entries. Although the @vmware list ids refer to VMware-internal mailing lists as opposed to email aliases, they serve a very similar purpose -- to inform VMware folks about patches to the relevant subsystems. Is there a consensus on how such lists should be specified? One suggestion (from Greg in the email thread referenced above) was to mark it as private, which is what this patch does. Maybe we can find a better alternative? How about specifying such lists using M: (indicating that this address can be used to reach maintainers), as long as that is not the only M: entry for a given subsystem (i.e., it includes real people's email id as well)? I think that would address Greg's primary objection too from that other thread (related to personal responsibility as maintainers). Regards, Srivatsa