From: Jerin Jacob <jerinjacobk@gmail.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dpdk-dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] maintainers: set git tree for test applications
Date: Tue, 14 Jan 2020 14:50:17 +0530 [thread overview]
Message-ID: <CALBAE1MjjjgJ-uk6hHfUuFSMbe6uB8+SU=VohmLOKhpBwS+dTg@mail.gmail.com> (raw)
In-Reply-To: <20200114091815.15052-1-david.marchand@redhat.com>
On Tue, Jan 14, 2020 at 2:48 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> Changes on the main test applications should be considered against
> subtrees where most of the API changes and development happen:
> - testpmd goes through dpdk-next-net as it is mainly about ethdev,
> - dpdk-test-compress-perf goes through dpdk-next-crypto since the
> compress API goes through this tree,
> - dpdk-test-crypto-perf through dpdk-next-crypto,
> - dpdk-test-eventdev through dpdk-next-eventdev,
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
> ---
> MAINTAINERS | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b7c4572d4c..b0cd0440ef 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1458,20 +1458,24 @@ Driver testing tool
> M: Wenzhuo Lu <wenzhuo.lu@intel.com>
> M: Jingjing Wu <jingjing.wu@intel.com>
> M: Bernard Iremonger <bernard.iremonger@intel.com>
> +T: git://dpdk.org/next/dpdk-next-net
> F: app/test-pmd/
> F: doc/guides/testpmd_app_ug/
>
> Compression performance test application
> +T: git://dpdk.org/next/dpdk-next-crypto
> F: app/test-compress-perf/
> F: doc/guides/tools/comp_perf.rst
>
> Crypto performance test application
> M: Declan Doherty <declan.doherty@intel.com>
> +T: git://dpdk.org/next/dpdk-next-crypto
> F: app/test-crypto-perf/
> F: doc/guides/tools/cryptoperf.rst
>
> Eventdev test application
> M: Jerin Jacob <jerinj@marvell.com>
> +T: git://dpdk.org/next/dpdk-next-eventdev
> F: app/test-eventdev/
> F: doc/guides/tools/testeventdev.rst
> F: doc/guides/tools/img/eventdev_*
> --
> 2.23.0
>
next prev parent reply other threads:[~2020-01-14 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 9:18 David Marchand
2020-01-14 9:20 ` Jerin Jacob [this message]
2020-01-14 10:12 ` Thomas Monjalon
2020-01-14 10:25 ` Ferruh Yigit
2020-01-14 13:57 ` Andrew Rybchenko
2020-01-22 21:41 ` Thomas Monjalon
2020-01-20 6:59 ` Akhil Goyal
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='CALBAE1MjjjgJ-uk6hHfUuFSMbe6uB8+SU=VohmLOKhpBwS+dTg@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=akhil.goyal@nxp.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.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).