From: Vishnu Dasa <vdasa@vmware.com>
To: Greg KH <gregkh@linuxfoundation.org>
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: Mon, 25 Jul 2022 18:29:25 +0000 [thread overview]
Message-ID: <FD326388-D2BB-42B4-B217-89DB9C134866@vmware.com> (raw)
In-Reply-To: <Yt7bfyANrfdPxdS8@kroah.com>
> 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.
>
>>
>> Acked-by: Bryan Tan <bryantan@vmware.com>
>> Signed-off-by: Vishnu Dasa <vdasa@vmware.com>
>
> I need an ack from the person that is being removed here, for obvious
> reasons. Any specific reason you didn't cc: them on this patch?
He is aware of this change, but we missed sending this patch before his
last day. So, his email ID is inactive now. Hence, it was omitted.
Please let me know if there's anything I can do.
next prev parent reply other threads:[~2022-07-25 18:29 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 [this message]
2022-07-26 15:10 ` Greg KH
2022-07-26 15:55 ` Vishnu Dasa
2022-07-26 16:18 ` Joe Perches
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=FD326388-D2BB-42B4-B217-89DB9C134866@vmware.com \
--to=vdasa@vmware.com \
--cc=Pv-drivers@vmware.com \
--cc=bryantan@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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®