From: Nadav Amit <namit@vmware.com>
To: "srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>
Cc: Joe Perches <joe@perches.com>, Juergen Gross <jgross@suse.com>,
X86 ML <x86@kernel.org>, Pv-drivers <Pv-drivers@vmware.com>,
Vivek Thampi <vithampi@vmware.com>,
Vishal Bhakta <vbhakta@vmware.com>,
Ronak Doshi <doshir@vmware.com>,
Linux-graphics-maintainer <Linux-graphics-maintainer@vmware.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Zack Rusin <zackr@vmware.com>, Deep Shah <sdeep@vmware.com>,
Alexey Makhalov <amakhalov@vmware.com>,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
Keerthana Kalyanasundaram <keerthanak@vmware.com>,
Srivatsa Bhat <srivatsab@vmware.com>,
Anish Swaminathan <anishs@vmware.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 2/2] MAINTAINERS: Mark VMware mailing list entries as private
Date: Wed, 10 Nov 2021 17:40:09 +0000 [thread overview]
Message-ID: <F21C4118-BFDE-4DA7-B42F-90EC71CFED57@vmware.com> (raw)
In-Reply-To: <20211110172000.GA121926@csail.mit.edu>
> On Nov 10, 2021, at 9:20 AM, Srivatsa S. Bhat <srivatsa@csail.mit.edu> wrote:
>
> On Tue, Nov 09, 2021 at 01:57:31PM -0800, Joe Perches wrote:
>> On Tue, 2021-11-09 at 00:58 +0000, Nadav Amit wrote:
>>>> On Nov 8, 2021, at 4:37 PM, Joe Perches <joe@perches.com> wrote:
>>>> On Mon, 2021-11-08 at 16:22 -0800, Srivatsa S. Bhat wrote:
>>>>
>>>> So it's an exploder not an actual maintainer and it likely isn't
>>>> publically archived with any normal list mechanism.
>>>>
>>>> So IMO "private" isn't appropriate. Neither is "L:"
>>>> Perhaps just mark it as what it is as an "exploder".
>>>>
>>>> Or maybe these blocks should be similar to:
>>>>
>>>> M: Name of Lead Developer <somebody@vmware.com>
>>>> M: VMware <foo> maintainers <linux-<foo>-maintainers@vmlinux.com>
>>
>> Maybe adding entries like
>>
>> M: Named maintainer <whoever@vmware.com>
>> R: VMware <foo> reviewers <linux-<foo>-maintainers@vmware.com>
>>
>> would be best/simplest.
>>
>
> Sure, that sounds good to me. I also considered adding "(email alias)"
> like Juergen suggested, but I think the R: entry is clear enough.
> Please find the updated patch below.
>
> ---
>
> From f66faa238facf504cfc66325912ce7af8cbf79ec Mon Sep 17 00:00:00 2001
> From: "Srivatsa S. Bhat (VMware)" <srivatsa@csail.mit.edu>
> Date: Mon, 8 Nov 2021 11:46:57 -0800
> Subject: [PATCH v2 2/2] MAINTAINERS: Mark VMware mailing list entries as email
> aliases
>
> VMware mailing lists in the MAINTAINERS file are private lists meant
> for VMware-internal review/notification for patches to the respective
> subsystems. Anyone can post to these addresses, but there is no public
> read access like open mailing lists, which makes them more like email
> aliases instead (to reach out to reviewers).
>
> So update all the VMware mailing list references in the MAINTAINERS
> file to mark them as such, using "R: email-alias@vmware.com".
>
> Signed-off-by: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
> Cc: Zack Rusin <zackr@vmware.com>
> 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
> ---
> MAINTAINERS | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 118cf8170d02..4372d79027e9 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>
> +R: VMware Graphics Reviewers <linux-graphics-maintainer@vmware.com>
> L: dri-devel@lists.freedesktop.org
> S: Supported
> T: git git://anongit.freedesktop.org/drm/drm-misc
> @@ -14189,7 +14189,7 @@ F: include/uapi/linux/ppdev.h
> PARAVIRT_OPS INTERFACE
> M: Juergen Gross <jgross@suse.com>
> M: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
> -L: pv-drivers@vmware.com (private)
> +R: VMware PV-Drivers Reviewers <pv-drivers@vmware.com>
This patch that you just sent seems to go on top of the previous patches
(as it removes "L: pv-drivers@vmware.com (private)”).
Since the patches were still not merged, I would presume you should squash
the old 2/2 with this new patch and send v3 of these patches.
next prev parent reply other threads:[~2021-11-10 17:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 20:29 [PATCH 1/2] MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor interface Srivatsa S. Bhat
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 [this message]
2021-11-10 19:13 ` Srivatsa S. Bhat
2021-11-09 5:34 ` Juergen Gross
2021-11-09 5:25 ` [PATCH 1/2] MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor interface Juergen Gross
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=F21C4118-BFDE-4DA7-B42F-90EC71CFED57@vmware.com \
--to=namit@vmware.com \
--cc=Linux-graphics-maintainer@vmware.com \
--cc=Pv-drivers@vmware.com \
--cc=amakhalov@vmware.com \
--cc=anishs@vmware.com \
--cc=doshir@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=jgross@suse.com \
--cc=joe@perches.com \
--cc=keerthanak@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=netdev@vger.kernel.org \
--cc=sdeep@vmware.com \
--cc=srivatsa@csail.mit.edu \
--cc=srivatsab@vmware.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®