From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] maintainers: add net-brcm sub-tree
Date: Thu, 17 Oct 2019 10:39:08 -0700 [thread overview]
Message-ID: <CACZ4nhuUz6Z8AwpxGOyb=MR+6wmC_XNXvkTHEqb1tdKvLKC5Dw@mail.gmail.com> (raw)
In-Reply-To: <20191015073800.29271-1-ferruh.yigit@intel.com>
On Tue, Oct 15, 2019 at 12:38 AM Ferruh Yigit <ferruh.yigit@intel.com>
wrote:
> Adding vendor specific sub-tree for Broadcom drivers.
> The next-net-brcm sub-tree will be sub-tree of the next-net.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Cc: Thomas Monjalon <thomas@monjalon.net>
>
Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> ---
> MAINTAINERS | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d2026b5ac8..1be286a15d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -45,6 +45,10 @@ Next-net-mlx Tree
> M: Raslan Darawsheh <rasland@mellanox.com>
> T: git://dpdk.org/next/dpdk-next-net-mlx
>
> +Next-net-brcm Tree
> +M: Ajit Khaparde <ajit.khaparde@broadcom.com>
> +T: git://dpdk.org/next/dpdk-next-net-brcm
> +
> Next-virtio Tree
> M: Maxime Coquelin <maxime.coquelin@redhat.com>
> M: Tiwei Bie <tiwei.bie@intel.com>
> @@ -565,6 +569,7 @@ F: doc/guides/nics/features/ark.ini
> Broadcom bnxt
> M: Ajit Khaparde <ajit.khaparde@broadcom.com>
> M: Somnath Kotur <somnath.kotur@broadcom.com>
> +T: git://dpdk.org/next/dpdk-next-net-brcm
> F: drivers/net/bnxt/
> F: doc/guides/nics/bnxt.rst
> F: doc/guides/nics/features/bnxt.ini
> --
> 2.21.0
>
>
next prev parent reply other threads:[~2019-10-17 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 7:38 Ferruh Yigit
2019-10-17 17:39 ` Ajit Khaparde [this message]
2019-10-17 21:23 ` Thomas Monjalon
2019-10-18 14:57 ` Ferruh Yigit
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='CACZ4nhuUz6Z8AwpxGOyb=MR+6wmC_XNXvkTHEqb1tdKvLKC5Dw@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
/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).