linux-rdma.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: linux-graphics-maintainer@vmware.com,
	Deep Shah <sdeep@vmware.com>, Joe Perches <joe@perches.com>,
	linux-rdma@vger.kernel.org, Ronak Doshi <doshir@vmware.com>,
	Nadav Amit <namit@vmware.com>,
	Alexey Makhalov <amakhalov@vmware.com>,
	Zack Rusin <zackr@vmware.com>,
	linux-input@vger.kernel.org, Vivek Thampi <vithampi@vmware.com>,
	linux-scsi@vger.kernel.org, Vishal Bhakta <vbhakta@vmware.com>,
	netdev@vger.kernel.org, dri-devel@lists.freedesktop.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 0/3] Update VMware maintainer entries
Date: Thu, 24 Feb 2022 14:23:48 -0800	[thread overview]
Message-ID: <164574138686.654750.10250173565414769119.stgit@csail.mit.edu> (raw)

This series updates a few maintainer entries for VMware-maintained
subsystems and cleans up references to VMware's private mailing lists
to make it clear that they are effectively email-aliases to reach out
to reviewers.

Changes from v4->v5:
- Add Alexey as reviewer for paravirt ops.

Changes from v3->v4:
- Remove Cc: stable@vger.kernel.org from patches 1 and 2.

Changes from v1->v3:
- Add Zack as the named maintainer for vmmouse driver
- Use R: to denote email-aliases for VMware reviewers

Regards,
Srivatsa
VMware Photon OS

---

Srivatsa S. Bhat (VMware) (3):
      MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor interface
      MAINTAINERS: Add Zack as maintainer of vmmouse driver
      MAINTAINERS: Mark VMware mailing list entries as email aliases


 MAINTAINERS | 31 ++++++++++++++++++-------------
 1 file changed, 18 insertions(+), 13 deletions(-)


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 22:23 Srivatsa S. Bhat [this message]
2022-02-24 22:24 ` [PATCH v5 3/3] MAINTAINERS: Mark VMware mailing list entries as email aliases Srivatsa S. Bhat
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=164574138686.654750.10250173565414769119.stgit@csail.mit.edu \
    --to=srivatsa@csail.mit.edu \
    --cc=amakhalov@vmware.com \
    --cc=anishs@vmware.com \
    --cc=bp@alien8.de \
    --cc=doshir@vmware.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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=linux-rdma@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=namit@vmware.com \
    --cc=netdev@vger.kernel.org \
    --cc=pv-drivers@vmware.com \
    --cc=rostedt@goodmis.org \
    --cc=sdeep@vmware.com \
    --cc=srivatsab@vmware.com \
    --cc=tglx@linutronix.de \
    --cc=vbhakta@vmware.com \
    --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).