From: Yong Wang <yongwang@vmware.com>
To: <dev@dpdk.org>
Cc: <skhare@vmware.com>, Yong Wang <yongwang@vmware.com>
Subject: [dpdk-dev] [PATCH] maintainers: claim responsibility for vmxnet3 pmd
Date: Fri, 30 Mar 2018 14:57:02 -0700 [thread overview]
Message-ID: <20180330215702.10933-1-yongwang@vmware.com> (raw)
Signed-off-by: Yong Wang <yongwang@vmware.com>
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 75d3e92c8..7bc370cf4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -552,7 +552,7 @@ F: doc/guides/nics/sfc_efx.rst
F: doc/guides/nics/features/sfc_efx.ini
VMware vmxnet3
-M: Shrikrishna Khare <skhare@vmware.com>
+M: Yong Wang <yongwang@vmware.com>
F: drivers/net/vmxnet3/
F: doc/guides/nics/vmxnet3.rst
F: doc/guides/nics/features/vmxnet3.ini
--
2.11.0
next reply other threads:[~2018-03-30 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 21:57 Yong Wang [this message]
2018-04-10 21:41 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2015-02-03 21:44 [dpdk-dev] [PATCH] maintainers: claim responsibility for VMXNET3 PMD Yong Wang
2015-02-09 14:40 ` Thomas Monjalon
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=20180330215702.10933-1-yongwang@vmware.com \
--to=yongwang@vmware.com \
--cc=dev@dpdk.org \
--cc=skhare@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).