From: vdasa--- via Virtualization <virtualization@lists.linux-foundation.org>
To: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
gregkh@linuxfoundation.org, pv-drivers@vmware.com,
bryantan@vmware.com
Cc: Vishnu Dasa <vdasa@vmware.com>
Subject: [PATCH] VMCI: Update maintainers for VMCI
Date: Mon, 25 Jul 2022 09:32:46 -0700 [thread overview]
Message-ID: <20220725163246.38486-1-vdasa@vmware.com> (raw)
From: Vishnu Dasa <vdasa@vmware.com>
Remove Rajesh as a maintainer for the VMCI driver.
Acked-by: Bryan Tan <bryantan@vmware.com>
Signed-off-by: Vishnu Dasa <vdasa@vmware.com>
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 25a9365e0cca..356fc4014c2a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -21706,7 +21706,6 @@ F: drivers/ptp/ptp_vmw.c
VMWARE VMCI DRIVER
M: Bryan Tan <bryantan@vmware.com>
-M: Rajesh Jalisatgi <rjalisatgi@vmware.com>
M: Vishnu Dasa <vdasa@vmware.com>
R: VMware PV-Drivers Reviewers <pv-drivers@vmware.com>
L: linux-kernel@vger.kernel.org
--
2.35.1
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next reply other threads:[~2022-07-25 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 16:32 vdasa--- via Virtualization [this message]
2022-07-25 18:05 ` [PATCH] VMCI: Update maintainers for VMCI Greg KH
2022-07-25 18:29 ` Vishnu Dasa via Virtualization
2022-07-26 15:10 ` Greg KH
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=20220725163246.38486-1-vdasa@vmware.com \
--to=virtualization@lists.linux-foundation.org \
--cc=bryantan@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=vdasa@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).