From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 1/3] MAINTAINERS remove experimental tag from vdev_netvsc
Date: Mon, 14 Sep 2020 19:03:39 -0700 [thread overview]
Message-ID: <20200915020341.28742-2-stephen@networkplumber.org> (raw)
In-Reply-To: <20200915020341.28742-1-stephen@networkplumber.org>
Vdev_netvsc has been around for several years. It no longer needs
to be marked experimental.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3b16d7a4b8c8..32db0996181f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -768,7 +768,7 @@ F: buildtools/options-ibverbs-static.sh
F: doc/guides/nics/mlx5.rst
F: doc/guides/nics/features/mlx5.ini
-Microsoft vdev_netvsc - EXPERIMENTAL
+Microsoft vdev_netvsc
M: Matan Azrad <matan@mellanox.com>
F: drivers/net/vdev_netvsc/
F: doc/guides/nics/vdev_netvsc.rst
--
2.27.0
next prev parent reply other threads:[~2020-09-15 2:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 2:03 [dpdk-dev] [PATCH 0/3] MAINTAINERS changes related to netvsc Stephen Hemminger
2020-09-15 2:03 ` Stephen Hemminger [this message]
2020-09-15 9:42 ` [dpdk-dev] [PATCH 1/3] MAINTAINERS remove experimental tag from vdev_netvsc Ferruh Yigit
2020-09-15 14:47 ` Stephen Hemminger
2020-10-05 22:41 ` Thomas Monjalon
2020-11-27 14:01 ` Thomas Monjalon
2020-11-28 17:40 ` Stephen Hemminger
2020-09-15 2:03 ` [dpdk-dev] [PATCH 2/3] MAINTAINERS - drop Kys and Haiyang Stephen Hemminger
2020-09-15 2:03 ` [dpdk-dev] [PATCH 3/3] MAINTAINERS - remove expermental tag of netvsd PMD Stephen Hemminger
2020-11-27 14:03 ` [dpdk-dev] [PATCH 0/3] MAINTAINERS changes related to netvsc 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=20200915020341.28742-2-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
/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).