From: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
To: jgross@suse.com, x86@kernel.org, pv-drivers@vmware.com
Cc: Zack Rusin <zackr@vmware.com>,
linux-graphics-maintainer@vmware.com,
linux-input@vger.kernel.org, amakhalov@vmware.com,
sdeep@vmware.com, virtualization@lists.linux-foundation.org,
keerthanak@vmware.com, srivatsab@vmware.com, anishs@vmware.com,
vithampi@vmware.com, linux-kernel@vger.kernel.org,
srivatsa@csail.mit.edu, namit@vmware.com, joe@perches.com,
kuba@kernel.org, rostedt@goodmis.org
Subject: [PATCH v3 2/3] MAINTAINERS: Add Zack as maintainer of vmmouse driver
Date: Wed, 10 Nov 2021 12:08:45 -0800 [thread overview]
Message-ID: <163657490344.84207.11803468380735093749.stgit@srivatsa-dev> (raw)
In-Reply-To: <163657479269.84207.13658789048079672839.stgit@srivatsa-dev>
From: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
Zack Rusin will be taking over the maintainership of the VMware
vmmouse driver. Update the MAINTAINERS file to reflect this change.
Signed-off-by: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
Acked-by: Zack Rusin <zackr@vmware.com>
Cc: linux-graphics-maintainer@vmware.com
Cc: pv-drivers@vmware.com
Cc: linux-input@vger.kernel.org
Cc: stable@vger.kernel.org
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0329d67c5bcf..21c0e49b80b9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -20079,6 +20079,7 @@ S: Maintained
F: drivers/misc/vmw_vmci/
VMWARE VMMOUSE SUBDRIVER
+M: Zack Rusin <zackr@vmware.com>
M: "VMware Graphics" <linux-graphics-maintainer@vmware.com>
M: "VMware, Inc." <pv-drivers@vmware.com>
L: linux-input@vger.kernel.org
next prev parent reply other threads:[~2021-11-10 20:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 20:07 [PATCH v3 0/3] Update VMware maintainer entries Srivatsa S. Bhat
2021-11-10 20:08 ` [PATCH v3 1/3] MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor interface Srivatsa S. Bhat
2021-11-11 6:50 ` Greg KH
2021-11-11 13:57 ` Steven Rostedt
2021-11-11 15:39 ` Srivatsa S. Bhat
2021-11-11 18:45 ` Greg KH
2021-11-11 19:40 ` Srivatsa S. Bhat
2021-11-12 6:55 ` Greg KH
2021-11-12 17:31 ` Srivatsa S. Bhat
2021-11-12 17:16 ` Sasha Levin
2021-11-15 22:39 ` Srivatsa S. Bhat
2021-11-16 4:33 ` Joe Perches
2021-11-16 18:18 ` Srivatsa S. Bhat
2021-11-16 23:11 ` Joe Perches
2021-11-10 20:08 ` Srivatsa S. Bhat [this message]
2021-11-10 20:09 ` [PATCH v3 3/3] MAINTAINERS: Mark VMware mailing list entries as email aliases Srivatsa S. Bhat
2021-11-11 1:39 ` Jakub Kicinski
2021-11-11 5:19 ` Joe Perches
[not found] ` <20211111055554.4f257fd2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
2021-11-12 17:50 ` Srivatsa S. Bhat
[not found] ` <20211112174458.GB11364@csail.mit.edu>
2021-11-12 17:52 ` Joe Perches
2021-11-11 13:46 ` 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=163657490344.84207.11803468380735093749.stgit@srivatsa-dev \
--to=srivatsa@csail.mit.edu \
--cc=amakhalov@vmware.com \
--cc=anishs@vmware.com \
--cc=jgross@suse.com \
--cc=joe@perches.com \
--cc=keerthanak@vmware.com \
--cc=kuba@kernel.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namit@vmware.com \
--cc=pv-drivers@vmware.com \
--cc=rostedt@goodmis.org \
--cc=sdeep@vmware.com \
--cc=srivatsab@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;
as well as URLs for NNTP newsgroup(s).