From: vdasa@vmware.com
To: vbhakta@vmware.com, namit@vmware.com, bryantan@vmware.com,
zackr@vmware.com, linux-graphics-maintainer@vmware.com,
doshir@vmware.com, sgarzare@redhat.com,
gregkh@linuxfoundation.org, davem@davemloft.net
Cc: pv-drivers@vmware.com, joe@perches.com, netdev@vger.kernel.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Vishnu Dasa <vdasa@vmware.com>
Subject: [PATCH 0/3] MAINTAINERS: Update entries for some VMware drivers
Date: Tue, 6 Sep 2022 10:27:19 -0700 [thread overview]
Message-ID: <20220906172722.19862-1-vdasa@vmware.com> (raw)
From: Vishnu Dasa <vdasa@vmware.com>
This series updates a few existing maintainer entries for VMware
supported drivers and adds a new entry for vsock vmci transport
driver.
Vishnu Dasa (3):
MAINTAINERS: Change VMware PVSCSI driver entry to upper case
MAINTAINERS: Change status of some VMware drivers
MAINTAINERS: Add a new entry for VMWARE VSOCK VMCI TRANSPORT DRIVER
MAINTAINERS | 26 +++++++++++++++++++-------
1 file changed, 19 insertions(+), 7 deletions(-)
--
2.35.1
WARNING: multiple messages have this Message-ID (diff)
From: vdasa--- via Virtualization <virtualization@lists.linux-foundation.org>
To: vbhakta@vmware.com, namit@vmware.com, bryantan@vmware.com,
zackr@vmware.com, linux-graphics-maintainer@vmware.com,
doshir@vmware.com, sgarzare@redhat.com,
gregkh@linuxfoundation.org, davem@davemloft.net
Cc: Vishnu Dasa <vdasa@vmware.com>,
linux-scsi@vger.kernel.org, pv-drivers@vmware.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-rdma@vger.kernel.org, linux-input@vger.kernel.org,
joe@perches.com
Subject: [PATCH 0/3] MAINTAINERS: Update entries for some VMware drivers
Date: Tue, 6 Sep 2022 10:27:19 -0700 [thread overview]
Message-ID: <20220906172722.19862-1-vdasa@vmware.com> (raw)
From: Vishnu Dasa <vdasa@vmware.com>
This series updates a few existing maintainer entries for VMware
supported drivers and adds a new entry for vsock vmci transport
driver.
Vishnu Dasa (3):
MAINTAINERS: Change VMware PVSCSI driver entry to upper case
MAINTAINERS: Change status of some VMware drivers
MAINTAINERS: Add a new entry for VMWARE VSOCK VMCI TRANSPORT DRIVER
MAINTAINERS | 26 +++++++++++++++++++-------
1 file changed, 19 insertions(+), 7 deletions(-)
--
2.35.1
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next reply other threads:[~2022-09-06 17:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 17:27 vdasa [this message]
2022-09-06 17:27 ` [PATCH 0/3] MAINTAINERS: Update entries for some VMware drivers vdasa--- via Virtualization
2022-09-06 17:27 ` [PATCH 1/3] MAINTAINERS: Change VMware PVSCSI driver entry to upper case vdasa
2022-09-06 17:27 ` vdasa--- via Virtualization
2022-09-06 17:27 ` [PATCH 2/3] MAINTAINERS: Change status of some VMware drivers vdasa
2022-09-06 17:27 ` vdasa--- via Virtualization
2022-09-06 17:37 ` Nadav Amit
2022-09-06 17:37 ` Nadav Amit via Virtualization
2022-09-06 17:27 ` [PATCH 3/3] MAINTAINERS: Add a new entry for VMWARE VSOCK VMCI TRANSPORT DRIVER vdasa
2022-09-06 17:27 ` vdasa--- via Virtualization
2022-09-07 7:45 ` Stefano Garzarella
2022-09-07 7:45 ` Stefano Garzarella
2022-09-07 7:51 ` [PATCH 0/3] MAINTAINERS: Update entries for some VMware drivers Stefano Garzarella
2022-09-07 7:51 ` Stefano Garzarella
2022-09-10 9:55 ` Vishnu Dasa
2022-09-10 9:55 ` Vishnu Dasa via Virtualization
2022-09-19 17:41 ` Jakub Kicinski
2022-09-20 8:18 ` Stefano Garzarella
2022-09-20 8:18 ` Stefano Garzarella
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=20220906172722.19862-1-vdasa@vmware.com \
--to=vdasa@vmware.com \
--cc=bryantan@vmware.com \
--cc=davem@davemloft.net \
--cc=doshir@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--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=sgarzare@redhat.com \
--cc=vbhakta@vmware.com \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.