From: Thomas Monjalon <thomas@monjalon.net>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] maintainers: add net-brcm sub-tree
Date: Thu, 17 Oct 2019 23:23:07 +0200 [thread overview]
Message-ID: <12088104.0xe1ukf1uQ@xps> (raw)
In-Reply-To: <CACZ4nhuUz6Z8AwpxGOyb=MR+6wmC_XNXvkTHEqb1tdKvLKC5Dw@mail.gmail.com>
17/10/2019 19:39, Ajit Khaparde:
> 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>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
next prev parent reply other threads:[~2019-10-17 21:23 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
2019-10-17 21:23 ` Thomas Monjalon [this message]
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=12088104.0xe1ukf1uQ@xps \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).