From: Long Li <longli@microsoft.com>
To: Wei Hu <weh@linux.microsoft.com>, "dev@dpdk.org" <dev@dpdk.org>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: Wei Hu <weh@microsoft.com>
Subject: RE: [PATCH 1/1] maintainers: update for vmbus/mana/netvsc drivers
Date: Thu, 27 Jun 2024 19:24:01 +0000 [thread overview]
Message-ID: <PH7PR21MB30711002A8A77B4B0271D930CED72@PH7PR21MB3071.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20240627105215.319935-1-weh@linux.microsoft.com>
> Subject: [PATCH 1/1] maintainers: update for vmbus/mana/netvsc drivers
>
> Add myself as maintainer for vmbus, mana and netvsc.
>
> Signed-off-by: Wei Hu <weh@microsoft.com>
Reviewed-by: Long Li <longli@microsoft.com>
> ---
> MAINTAINERS | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c9adff9846..58947b57ce 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -624,6 +624,7 @@ F: app/test/test_vdev.c
>
> VMBUS bus driver
> M: Long Li <longli@microsoft.com>
> +M: Wei Hu <weh@microsoft.com>
> F: drivers/bus/vmbus/
>
>
> @@ -882,6 +883,7 @@ F: doc/guides/nics/features/mlx5.ini
>
> Microsoft mana
> M: Long Li <longli@microsoft.com>
> +M: Wei Hu <weh@microsoft.com>
> F: drivers/net/mana/
> F: doc/guides/nics/mana.rst
> F: doc/guides/nics/features/mana.ini
> @@ -893,6 +895,7 @@ F: doc/guides/nics/vdev_netvsc.rst
>
> Microsoft Hyper-V netvsc
> M: Long Li <longli@microsoft.com>
> +M: Wei Hu <weh@microsoft.com>
> F: drivers/net/netvsc/
> F: doc/guides/nics/netvsc.rst
> F: doc/guides/nics/features/netvsc.ini
> --
> 2.34.1
next prev parent reply other threads:[~2024-06-27 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 10:52 Wei Hu
2024-06-27 19:24 ` Long Li [this message]
2024-07-12 17:07 ` David Marchand
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=PH7PR21MB30711002A8A77B4B0271D930CED72@PH7PR21MB3071.namprd21.prod.outlook.com \
--to=longli@microsoft.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=thomas@monjalon.net \
--cc=weh@linux.microsoft.com \
--cc=weh@microsoft.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).