From: Thomas Monjalon <thomas@monjalon.net>
To: jerinj@marvell.com
Cc: dev@dpdk.org, ferruh.yigit@intel.com, david.marchand@redhat.com,
Jerin Jacob <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] maintainers: update for OCTEON TX2 common driver tree
Date: Tue, 30 Jun 2020 17:04:14 +0200 [thread overview]
Message-ID: <6202529.Y7CoasJeLS@thomas> (raw)
In-Reply-To: <20200630150130.4191883-1-jerinj@marvell.com>
30/06/2020 17:01, jerinj@marvell.com:
> From: Jerin Jacob <jerinj@marvell.com>
>
> drivers/common/octeontx2 changes are merged through the main tree.
> To reduce driver-specific code merge through the main tree and
> the common code changes are mostly related to networking,
> update the common code tree as dpdk-next-net-mrvl.
>
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> ---
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -504,10 +504,7 @@ F: drivers/mempool/bucket/
> Marvell OCTEON TX2
> M: Jerin Jacob <jerinj@marvell.com>
> M: Nithin Dabilpuram <ndabilpuram@marvell.com>
> -F: drivers/common/octeontx2/
> F: drivers/mempool/octeontx2/
> -F: doc/guides/platform/img/octeontx2_*
> -F: doc/guides/platform/octeontx2.rst
> F: doc/guides/mempool/octeontx2.rst
I would imagine adding T: git://dpdk.org/next/dpdk-next-net-mrvl
on top of this section and keeps everything in it.
Opinion about this alternative?
> @@ -753,8 +750,11 @@ M: Nithin Dabilpuram <ndabilpuram@marvell.com>
> M: Kiran Kumar K <kirankumark@marvell.com>
> T: git://dpdk.org/next/dpdk-next-net-mrvl
> F: drivers/net/octeontx2/
> +F: drivers/common/octeontx2/
> F: doc/guides/nics/features/octeontx2*.ini
> F: doc/guides/nics/octeontx2.rst
> +F: doc/guides/platform/img/octeontx2_*
> +F: doc/guides/platform/octeontx2.rst
prev parent reply other threads:[~2020-06-30 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 15:01 jerinj
2020-06-30 15:04 ` Thomas Monjalon [this message]
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=6202529.Y7CoasJeLS@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.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).