DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/eventdev: fix test pipeline meson build
Date: Sat, 15 Feb 2020 13:21:43 +0530	[thread overview]
Message-ID: <CALBAE1N6ksr+_q=a6fBvsfgaSmDh1NejJBkr4=YKY5nhmScX-A@mail.gmail.com> (raw)
In-Reply-To: <20200203045300.5079-1-pbhagavatula@marvell.com>

On Mon, Feb 3, 2020 at 10:23 AM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Add missing pipeline test to meson build.
>
> Fixes: 2ff67267b049 ("app/eventdev: build with meson")
Cc: stable@dpdk.org

>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-eventdev/master. Thanks.


> ---
>  app/test-eventdev/meson.build | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/app/test-eventdev/meson.build b/app/test-eventdev/meson.build
> index 7ff2b786c..9e588d9ec 100644
> --- a/app/test-eventdev/meson.build
> +++ b/app/test-eventdev/meson.build
> @@ -10,5 +10,8 @@ sources = files('evt_main.c',
>                 'test_order_queue.c',
>                 'test_perf_common.c',
>                 'test_perf_atq.c',
> -               'test_perf_queue.c')
> +               'test_perf_queue.c',
> +               'test_pipeline_common.c',
> +               'test_pipeline_atq.c',
> +               'test_pipeline_queue.c')
>  deps += 'eventdev'
> --
> 2.17.1
>

      reply	other threads:[~2020-02-15  7:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03  4:52 pbhagavatula
2020-02-15  7:51 ` Jerin Jacob [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='CALBAE1N6ksr+_q=a6fBvsfgaSmDh1NejJBkr4=YKY5nhmScX-A@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@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).