From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
"Jerin Jacob Kollanukkaran" <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 3/3] app/eventdev: follow proper teardown sequence
Date: Mon, 11 Mar 2019 09:58:13 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA6757FE7AA@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <20190301071617.6570-3-pbhagavatula@marvell.com>
> -----Original Message-----
> From: Pavan Nikhilesh Bhagavatula [mailto:pbhagavatula@marvell.com]
> Sent: Friday, March 1, 2019 7:17 AM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Van Haaren, Harry
> <harry.van.haaren@intel.com>
> Cc: dev@dpdk.org; Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
> Subject: [dpdk-dev] [PATCH 3/3] app/eventdev: follow proper teardown
> sequence
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Stop eventdev before closing it.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
next prev parent reply other threads:[~2019-03-11 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 7:16 [dpdk-dev] [PATCH 1/3] examples/eventdev_pipeline: configure max events based on dev info Pavan Nikhilesh Bhagavatula
2019-03-01 7:16 ` [dpdk-dev] [PATCH 2/3] examples/eventdev_pipeline: follow proper teardown sequence Pavan Nikhilesh Bhagavatula
2019-03-11 9:57 ` Van Haaren, Harry
2019-03-01 7:16 ` [dpdk-dev] [PATCH 3/3] app/eventdev: " Pavan Nikhilesh Bhagavatula
2019-03-11 9:58 ` Van Haaren, Harry [this message]
2019-03-11 15:12 ` Jerin Jacob Kollanukkaran
2019-03-08 18:25 ` [dpdk-dev] [PATCH 1/3] examples/eventdev_pipeline: configure max events based on dev info Jerin Jacob Kollanukkaran
2019-03-11 9:57 ` Van Haaren, Harry
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=E923DB57A917B54B9182A2E928D00FA6757FE7AA@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.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).