From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev][PATCH 1/2] app/eventdev: fix order test port creation
Date: Tue, 2 Jul 2019 05:28:30 +0000 [thread overview]
Message-ID: <BYAPR18MB2424813068E83E6E71C1DC05C8F80@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20190630175240.1126-1-pbhagavatula@marvell.com>
> -----Original Message-----
> From: pbhagavatula@marvell.com <pbhagavatula@marvell.com>
> Sent: Sunday, June 30, 2019 11:23 PM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> Cc: dev@dpdk.org; Pavan Nikhilesh Bhagavatula
> <pbhagavatula@marvell.com>; stable@dpdk.org
> Subject: [dpdk-dev][PATCH 1/2] app/eventdev: fix order test port creation
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Configure event ports based on the underlying event device info rather than
> using hardcoded values.
>
> Cc: stable@dpdk.org
> Fixes: 5710e751813e ("app/testeventdev: add order port setup")
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
prev parent reply other threads:[~2019-07-02 5:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 17:52 pbhagavatula
2019-06-30 17:52 ` [dpdk-stable] [dpdk-dev][PATCH 2/2] test/eventdev: fix producer core validity checks pbhagavatula
2019-07-02 5:29 ` Jerin Jacob Kollanukkaran
2019-07-02 14:20 ` [dpdk-stable] [dpdk-dev] [PATCH " Jerin Jacob Kollanukkaran
2019-07-02 5:28 ` Jerin Jacob Kollanukkaran [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=BYAPR18MB2424813068E83E6E71C1DC05C8F80@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=pbhagavatula@marvell.com \
--cc=stable@dpdk.org \
/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).