From: Greg KH <gregkh@linuxfoundation.org>
To: Vishnu Dasa <vdasa@vmware.com>
Cc: Pv-drivers <Pv-drivers@vmware.com>,
Bryan Tan <bryantan@vmware.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] VMCI: Update maintainers for VMCI
Date: Tue, 26 Jul 2022 17:10:47 +0200 [thread overview]
Message-ID: <YuAD90UfLnf1Ojso@kroah.com> (raw)
In-Reply-To: <FD326388-D2BB-42B4-B217-89DB9C134866@vmware.com>
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.
thanks,
greg k-h
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-07-26 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 16:32 [PATCH] VMCI: Update maintainers for VMCI vdasa--- via Virtualization
2022-07-25 18:05 ` Greg KH
2022-07-25 18:29 ` Vishnu Dasa via Virtualization
2022-07-26 15:10 ` Greg KH [this message]
2022-07-26 15:55 ` Vishnu Dasa via Virtualization
2022-07-26 16:18 ` Joe Perches
2022-07-26 17:10 ` Vishnu Dasa via Virtualization
[not found] ` <CAJ60do+Lgnx6gfHncckF-=8F=zzn81tCiFNLOmg_8TyuLGUotw@mail.gmail.com>
2022-07-28 8:44 ` Greg KH
-- 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=YuAD90UfLnf1Ojso@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Pv-drivers@vmware.com \
--cc=bryantan@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).