From: Stefano Garzarella <sgarzare@redhat.com>
To: vdasa@vmware.com
Cc: vbhakta@vmware.com, namit@vmware.com, bryantan@vmware.com,
zackr@vmware.com, linux-graphics-maintainer@vmware.com,
doshir@vmware.com, gregkh@linuxfoundation.org,
davem@davemloft.net, 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
Subject: Re: [PATCH 0/3] MAINTAINERS: Update entries for some VMware drivers
Date: Wed, 7 Sep 2022 09:51:38 +0200 [thread overview]
Message-ID: <20220907075138.ph3bbitnev72rei3@sgarzare-redhat> (raw)
In-Reply-To: <20220906172722.19862-1-vdasa@vmware.com>
On Tue, Sep 06, 2022 at 10:27:19AM -0700, vdasa@vmware.com wrote:
>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.
>
Since you are updating MAINTAINERS, what about adding
"include/linux/vmw_vmci*" under "VMWARE VMCI DRIVER"?
Thanks,
Stefano
next prev parent reply other threads:[~2022-09-07 7:52 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
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 ` Stefano Garzarella [this message]
2022-09-10 9:55 ` [PATCH 0/3] MAINTAINERS: Update entries for some VMware drivers 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=20220907075138.ph3bbitnev72rei3@sgarzare-redhat \
--to=sgarzare@redhat.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=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;
as well as URLs for NNTP newsgroup(s).