linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
To: jgross@suse.com, x86@kernel.org, pv-drivers@vmware.com,
	tglx@linutronix.de, bp@alien8.de
Cc: Zack Rusin <zackr@vmware.com>,
	linux-graphics-maintainer@vmware.com,
	linux-input@vger.kernel.org, sdeep@vmware.com,
	vithampi@vmware.com, amakhalov@vmware.com, keerthanak@vmware.com,
	srivatsab@vmware.com, anishs@vmware.com,
	linux-kernel@vger.kernel.org, namit@vmware.com, joe@perches.com,
	kuba@kernel.org, rostedt@goodmis.org, srivatsa@csail.mit.edu
Subject: [PATCH v5 2/3] MAINTAINERS: Add Zack as maintainer of vmmouse driver
Date: Thu, 24 Feb 2022 14:24:36 -0800	[thread overview]
Message-ID: <164574146977.654750.10918397477833459687.stgit@csail.mit.edu> (raw)
In-Reply-To: <164574138686.654750.10250173565414769119.stgit@csail.mit.edu>

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
---

 MAINTAINERS |    1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 9325debf5365..72771881f159 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -20690,6 +20690,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



  parent reply	other threads:[~2022-02-24 22:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 22:23 [PATCH v5 0/3] Update VMware maintainer entries Srivatsa S. Bhat
2022-02-24 22:24 ` [PATCH v5 1/3] MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor interface Srivatsa S. Bhat
2022-02-25 13:10   ` Juergen Gross
2022-03-15 17:05   ` [tip: x86/misc] " tip-bot2 for Srivatsa S. Bhat (VMware)
2022-02-24 22:24 ` Srivatsa S. Bhat [this message]
2022-03-15 17:05   ` [tip: x86/misc] MAINTAINERS: Add Zack as maintainer of vmmouse driver tip-bot2 for Srivatsa S. Bhat (VMware)
2022-02-24 22:24 ` [PATCH v5 3/3] MAINTAINERS: Mark VMware mailing list entries as email aliases Srivatsa S. Bhat
2022-03-15 17:05   ` [tip: x86/misc] " tip-bot2 for Srivatsa S. Bhat (VMware)
2022-03-07 17:06 ` [PATCH v5 0/3] Update VMware maintainer entries Srivatsa S. Bhat

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=164574146977.654750.10918397477833459687.stgit@csail.mit.edu \
    --to=srivatsa@csail.mit.edu \
    --cc=amakhalov@vmware.com \
    --cc=anishs@vmware.com \
    --cc=bp@alien8.de \
    --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=tglx@linutronix.de \
    --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).