From: Juergen Gross <jgross@suse.com>
To: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>,
x86@kernel.org, pv-drivers@vmware.com
Cc: Nadav Amit <namit@vmware.com>, Vivek Thampi <vithampi@vmware.com>,
Vishal Bhakta <vbhakta@vmware.com>,
Ronak Doshi <doshir@vmware.com>,
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 <zackr@vmware.com>,
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
Subject: Re: [PATCH 2/2] MAINTAINERS: Mark VMware mailing list entries as private
Date: Tue, 9 Nov 2021 06:34:31 +0100 [thread overview]
Message-ID: <05804bc2-60fb-b1f8-c0c4-ad7b1c45462a@suse.com> (raw)
In-Reply-To: <163640339370.62866.3435211389009241865.stgit@srivatsa-dev>
[-- Attachment #1.1.1: Type: text/plain, Size: 3076 bytes --]
On 08.11.21 21:30, Srivatsa S. Bhat wrote:
> From: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
>
> 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)".
>
> [1]. https://lore.kernel.org/r/YPfp0Ff6KuyPlyrc@kroah.com
> [2]. https://lore.kernel.org/r/1626861766-11115-1-git-send-email-jhansen@vmware.com
>
> Signed-off-by: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
> Cc: Nadav Amit <namit@vmware.com>
> Cc: Vivek Thampi <vithampi@vmware.com>
> Cc: Vishal Bhakta <vbhakta@vmware.com>
> Cc: Ronak Doshi <doshir@vmware.com>
> Cc: pv-drivers@vmware.com
> Cc: linux-graphics-maintainer@vmware.com
> Cc: dri-devel@lists.freedesktop.org
> Cc: linux-rdma@vger.kernel.org
> Cc: linux-scsi@vger.kernel.org
> Cc: netdev@vger.kernel.org
> Cc: linux-input@vger.kernel.org
> Acked-by: Zack Rusin <zackr@vmware.com>
> ---
>
> MAINTAINERS | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 118cf8170d02..3e92176e68fb 100644
> --- 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" <linux-graphics-maintainer@vmware.com>
> M: Zack Rusin <zackr@vmware.com>
> +L: linux-graphics-maintainer@vmware.com (private)
> L: dri-devel@lists.freedesktop.org
> S: Supported
> T: git git://anongit.freedesktop.org/drm/drm-misc
> @@ -20032,7 +20032,7 @@ F: tools/testing/vsock/
>
> VMWARE BALLOON DRIVER
> M: Nadav Amit <namit@vmware.com>
> -M: "VMware, Inc." <pv-drivers@vmware.com>
> +L: pv-drivers@vmware.com (private)
> L: linux-kernel@vger.kernel.org
> S: Maintained
> F: drivers/misc/vmw_balloon.c
> @@ -20050,14 +20050,14 @@ F: arch/x86/kernel/cpu/vmware.c
>
> VMWARE PVRDMA DRIVER
> M: Adit Ranadive <aditr@vmware.com>
> -M: VMware PV-Drivers <pv-drivers@vmware.com>
> +L: pv-drivers@vmware.com (private)
> L: linux-rdma@vger.kernel.org
> S: Maintained
> F: drivers/infiniband/hw/vmw_pvrdma/
>
> VMware PVSCSI driver
> M: Vishal Bhakta <vbhakta@vmware.com>
> -M: VMware PV-Drivers <pv-drivers@vmware.com>
> +L: pv-drivers@vmware.com (private)
> L: linux-scsi@vger.kernel.org
> S: Maintained
> F: drivers/scsi/vmw_pvscsi.c
> @@ -20065,7 +20065,7 @@ F: drivers/scsi/vmw_pvscsi.h
>
> VMWARE VIRTUAL PTP CLOCK DRIVER
> M: Vivek Thampi <vithampi@vmware.com>
> -M: "VMware, Inc." <pv-drivers@vmware.com>
> +L: pv-drivers@vmware.com (private)
Maybe replace "(private)" with "(mail alias)"?
This makes it rather clear that it is a valid address to send patches
to, but there isn't public read access like to a ML.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3135 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2021-11-09 5:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <163640336232.62866.489924062999332446.stgit@srivatsa-dev>
2021-11-08 20:30 ` [PATCH 2/2] MAINTAINERS: Mark VMware mailing list entries as private Srivatsa S. Bhat
2021-11-08 20:45 ` Nadav Amit
2021-11-08 23:37 ` Joe Perches
2021-11-09 0:16 ` Jakub Kicinski
2021-11-09 0:22 ` Joe Perches
2021-11-09 0:22 ` Srivatsa S. Bhat
2021-11-09 0:37 ` Joe Perches
2021-11-09 0:58 ` Nadav Amit
2021-11-09 21:57 ` Joe Perches
2021-11-10 17:20 ` Srivatsa S. Bhat
2021-11-10 17:40 ` Nadav Amit
2021-11-10 19:13 ` Srivatsa S. Bhat
2021-11-09 5:34 ` Juergen Gross [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=05804bc2-60fb-b1f8-c0c4-ad7b1c45462a@suse.com \
--to=jgross@suse.com \
--cc=amakhalov@vmware.com \
--cc=anishs@vmware.com \
--cc=doshir@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=keerthanak@vmware.com \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=namit@vmware.com \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=sdeep@vmware.com \
--cc=srivatsa@csail.mit.edu \
--cc=srivatsab@vmware.com \
--cc=vbhakta@vmware.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=vithampi@vmware.com \
--cc=x86@kernel.org \
--cc=zackr@vmware.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 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).