From: Joe Perches <joe@perches.com>
To: Vishnu Dasa <vdasa@vmware.com>,
Greg KH <gregkh@linuxfoundation.org>,
"rajeshjalisatgi@gmail.com" <rajeshjalisatgi@gmail.com>
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>,
Bryan Tan <bryantan@vmware.com>
Subject: Re: [PATCH] VMCI: Update maintainers for VMCI
Date: Tue, 26 Jul 2022 09:18:15 -0700 [thread overview]
Message-ID: <1c536f8e9666725ce9f3eb97acc34d08f38d2095.camel@perches.com> (raw)
In-Reply-To: <47D07B41-C327-4908-A383-683FC6C67040@vmware.com>
On Tue, 2022-07-26 at 15:55 +0000, Vishnu Dasa wrote:
> > On Jul 26, 2022, at 8:10 AM, Greg KH <gregkh@linuxfoundation.org wrote:
> > On Mon, Jul 25, 2022 at 06:29:25PM +0000, Vishnu Dasa wrote:
> > > > On Jul 25, 2022, at 11:05 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > > > On Mon, Jul 25, 2022 at 09:32:46AM -0700, vdasa@vmware.com wrote:
> > > > > From: Vishnu Dasa <vdasa@vmware.com>
> > > > > Remove Rajesh as a maintainer for the VMCI driver.
> > > > Why?
> > > Rajesh is no longer with VMware and won't be working on VMCI.
> >
> > But employment does not matter for maintainership and has nothing to do
> > with it. Maintainership follows the person, not the company, you all
> > know this.
> >
> > So for obvious reasons, I can't take this type of change without
> > Rajesh acking it.
>
> I understand. After getting in touch with Rajesh, cc'ing him via his
> personal email ID.
>
> Rajesh, could you please provide your ack if you agree with this patch to
> remove you as the maintainer for VMCI?
If being an employee of a company is a criteria for maintainership
of this subsystem, likely the subsystem entry should be:
"S: Supported" not "S: Maintained"
MAINTAINERS:VMWARE VMCI DRIVER
MAINTAINERS-M: Bryan Tan <bryantan@vmware.com>
MAINTAINERS-M: Rajesh Jalisatgi <rjalisatgi@vmware.com>
MAINTAINERS-M: Vishnu Dasa <vdasa@vmware.com>
MAINTAINERS-R: VMware PV-Drivers Reviewers <pv-drivers@vmware.com>
MAINTAINERS-L: linux-kernel@vger.kernel.org
MAINTAINERS-S: Maintained
Likely that's true for every VMware entry.
MAINTAINERS:VMWARE BALLOON DRIVER
MAINTAINERS-M: Nadav Amit <namit@vmware.com>
MAINTAINERS-R: VMware PV-Drivers Reviewers <pv-drivers@vmware.com>
MAINTAINERS-L: linux-kernel@vger.kernel.org
MAINTAINERS-S: Maintained
MAINTAINERS-F: drivers/misc/vmw_balloon.c
MAINTAINERS-
MAINTAINERS:VMWARE PVRDMA DRIVER
MAINTAINERS-M: Bryan Tan <bryantan@vmware.com>
MAINTAINERS-M: Vishnu Dasa <vdasa@vmware.com>
MAINTAINERS-R: VMware PV-Drivers Reviewers <pv-drivers@vmware.com>
MAINTAINERS-L: linux-rdma@vger.kernel.org
MAINTAINERS-S: Maintained
MAINTAINERS-F: drivers/infiniband/hw/vmw_pvrdma/
MAINTAINERS-
MAINTAINERS-VMware PVSCSI driver
MAINTAINERS-M: Vishal Bhakta <vbhakta@vmware.com>
MAINTAINERS-R: VMware PV-Drivers Reviewers <pv-drivers@vmware.com>
MAINTAINERS-L: linux-scsi@vger.kernel.org
MAINTAINERS-S: Maintained
MAINTAINERS-F: drivers/scsi/vmw_pvscsi.c
MAINTAINERS-F: drivers/scsi/vmw_pvscsi.h
MAINTAINERS-
MAINTAINERS:VMWARE VMMOUSE SUBDRIVER
MAINTAINERS-M: Zack Rusin <zackr@vmware.com>
MAINTAINERS-R: VMware Graphics Reviewers <linux-graphics-maintainer@vmware.com>
MAINTAINERS-R: VMware PV-Drivers Reviewers <pv-drivers@vmware.com>
MAINTAINERS-L: linux-input@vger.kernel.org
MAINTAINERS-S: Maintained
MAINTAINERS-F: drivers/input/mouse/vmmouse.c
MAINTAINERS-F: drivers/input/mouse/vmmouse.h
MAINTAINERS-
MAINTAINERS:VMWARE VMXNET3 ETHERNET DRIVER
MAINTAINERS-M: Ronak Doshi <doshir@vmware.com>
MAINTAINERS-R: VMware PV-Drivers Reviewers <pv-drivers@vmware.com>
MAINTAINERS-L: netdev@vger.kernel.org
MAINTAINERS-S: Maintained
MAINTAINERS-F: drivers/net/vmxnet3/
MAINTAINERS-
next prev parent reply other threads:[~2022-07-26 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 16:32 vdasa
2022-07-25 18:05 ` Greg KH
2022-07-25 18:29 ` Vishnu Dasa
2022-07-26 15:10 ` Greg KH
2022-07-26 15:55 ` Vishnu Dasa
2022-07-26 16:18 ` Joe Perches [this message]
2022-07-26 17:10 ` Vishnu Dasa
[not found] ` <CAJ60do+Lgnx6gfHncckF-=8F=zzn81tCiFNLOmg_8TyuLGUotw@mail.gmail.com>
2022-07-28 8:44 ` Greg KH
[not found] ` <CAJ60doKSPJbvXoTZDfSmaAV5Sh3-RiqtTUw73S3R3TBknLmqDA@mail.gmail.com>
2022-08-01 18:09 ` Fwd: " rajesh jalisatgi
-- strict thread matches above, loose matches on Subject: below --
2022-02-27 21:05 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=1c536f8e9666725ce9f3eb97acc34d08f38d2095.camel@perches.com \
--to=joe@perches.com \
--cc=Pv-drivers@vmware.com \
--cc=bryantan@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajeshjalisatgi@gmail.com \
--cc=vdasa@vmware.com \
--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
all inboxes | Powered by JetHome®