From: "Varghese, Vipin" <vipin.varghese@intel.com>
To: "Rao, Nikhil" <nikhil.rao@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Jain, Deepak K" <deepak.k.jain@intel.com>
Subject: Re: [dpdk-dev] [PATCH] test/eventdev: add multi port test to suite
Date: Mon, 21 May 2018 11:00:06 +0000 [thread overview]
Message-ID: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D1F7C93@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <875b1678-b7bc-ca2e-b11f-c9f9bc33b9aa@intel.com>
Hi Nikhil,
Thanks for the inputs, I have shared the V2 with suggested changes. As for
<snipped>
+ adapter_free();
Is it necessary to call adapter_free() above ?
<Snipped>
With the changes suggested above
Acked-by: Nikhil Rao <nikhil.rao@intel.com><mailto:nikhil.rao@intel.com>
Yes it not required by current test sequence. This is added for safety, in case in previous free is incomplete or interrupted.
next prev parent reply other threads:[~2018-05-21 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 10:17 Vipin Varghese
2018-05-18 5:19 ` Rao, Nikhil
2018-05-21 11:00 ` Varghese, Vipin [this message]
2018-05-21 11:39 ` Rao, Nikhil
2018-05-21 13:54 ` Varghese, Vipin
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=4C9E0AB70F954A408CC4ADDBF0F8FA7D4D1F7C93@BGSMSX101.gar.corp.intel.com \
--to=vipin.varghese@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=nikhil.rao@intel.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).