From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, Jerin Jacob <jerinjacobk@gmail.com>,
Jerin Jacob <jerinj@marvell.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
Andrew Rybchenko <arybchenko@solarflare.com>
Subject: Re: [dpdk-dev] [PATCH] maintainers: set git tree for test applications
Date: Wed, 22 Jan 2020 22:41:38 +0100 [thread overview]
Message-ID: <6294798.ZlIXO0BPYK@xps> (raw)
In-Reply-To: <c6e7a354-457d-9dca-8b04-d03a3d9276b1@solarflare.com>
14/01/2020 14:57, Andrew Rybchenko:
> On 1/14/20 1:25 PM, Ferruh Yigit wrote:
> > On 1/14/2020 10:12 AM, Thomas Monjalon wrote:
> >> 14/01/2020 10:20, Jerin Jacob:
> >>> 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>
> >>
> >> Acked-by: Thomas Monjalon <thomas@monjalon.net>
> >
> > Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Most acked patch :-)
Applied, thanks
next prev parent reply other threads:[~2020-01-22 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 9:18 [dpdk-dev] [PATCH] maintainers: set git tree for test applications David Marchand
2020-01-14 9:20 ` Jerin Jacob
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 [this message]
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=6294798.ZlIXO0BPYK@xps \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=arybchenko@solarflare.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.