From: Nadav Amit <namit@vmware.com>
To: Vishnu Dasa <vdasa@vmware.com>
Cc: Vishal Bhakta <vbhakta@vmware.com>,
Bryan Tan <bryantan@vmware.com>, Zack Rusin <zackr@vmware.com>,
Linux-graphics-maintainer <Linux-graphics-maintainer@vmware.com>,
Ronak Doshi <doshir@vmware.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"davem@davemloft.net" <davem@davemloft.net>,
Pv-drivers <Pv-drivers@vmware.com>, Joe Perches <joe@perches.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 2/3] MAINTAINERS: Change status of some VMware drivers
Date: Tue, 6 Sep 2022 17:37:43 +0000 [thread overview]
Message-ID: <4269C33A-AC6E-4247-8471-5AC0A7D3DB1C@vmware.com> (raw)
In-Reply-To: <20220906172722.19862-3-vdasa@vmware.com>
On Sep 6, 2022, at 10:27 AM, Vishnu Dasa <vdasa@vmware.com> wrote:
> From: Vishnu Dasa <vdasa@vmware.com>
>
> Change the status from 'Maintained' to 'Supported' for VMWARE
> BALLOON DRIVER, VMWARE PVRDMA DRIVER, VMWARE PVSCSI driver,
> VMWARE VMCI DRIVER, VMWARE VMMOUSE SUBDRIVER and VMWARE VMXNET3
> ETHERNET DRIVER.
>
> This needs to be done to conform to the guidelines in [1].
> Maintainers for these drivers are VMware employees.
>
> [1] https://docs.kernel.org/process/maintainers.html
>
> Signed-off-by: Vishnu Dasa <vdasa@vmware.com>
> ---
> MAINTAINERS | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b75eb23a099b..5a634b5d6f6c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -21812,7 +21812,7 @@ VMWARE BALLOON DRIVER
> M: Nadav Amit <namit@vmware.com>
> R: VMware PV-Drivers Reviewers <pv-drivers@vmware.com>
> L: linux-kernel@vger.kernel.org
> -S: Maintained
> +S: Supported
> F: drivers/misc/vmw_balloon.c
Acked-by: Nadav Amit <namit@vmware.com>
next prev parent reply other threads:[~2022-09-06 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 17:27 [PATCH 0/3] MAINTAINERS: Update entries for some VMware drivers vdasa
2022-09-06 17:27 ` [PATCH 1/3] MAINTAINERS: Change VMware PVSCSI driver entry to upper case vdasa
2022-09-06 17:27 ` [PATCH 2/3] MAINTAINERS: Change status of some VMware drivers vdasa
2022-09-06 17:37 ` Nadav Amit [this message]
2022-09-06 17:27 ` [PATCH 3/3] MAINTAINERS: Add a new entry for VMWARE VSOCK VMCI TRANSPORT DRIVER vdasa
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-10 9:55 ` Vishnu Dasa
2022-09-19 17:41 ` Jakub Kicinski
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=4269C33A-AC6E-4247-8471-5AC0A7D3DB1C@vmware.com \
--to=namit@vmware.com \
--cc=Linux-graphics-maintainer@vmware.com \
--cc=Pv-drivers@vmware.com \
--cc=bryantan@vmware.com \
--cc=davem@davemloft.net \
--cc=doshir@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.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=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=vbhakta@vmware.com \
--cc=vdasa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox