From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] test: store only the test case name
Date: Mon, 20 Mar 2017 10:14:38 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA6129FE9C8@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <20170320100429.jf2lpdpybb6tt4yl@localhost.localdomain>
> From: Jerin Jacob [mailto:jerin.jacob@caviumnetworks.com]
> > It looks like the patch got corrupted somehow - the above line should be
> app/test/test.c, not test/test/test.c
> > Applying fails here, but with a s/test/app in the right places, the patches (this and
> next) both apply cleanly, and work well.
> > This handles the event/sw timeout_ticks() unsupported function as should so,
> >
> > Tested-by: Harry van Haaren <harry.van.haaren@intel.com>
> >
> >
> > With the above apply issue resolved, also
>
> Recently there was a rework in test directory. Now test/test points to old app/test
> in dpdk-master.So no issues.
>
> http://dpdk.org/browse/dpdk/tree/test/test
Ah, I'm behind on master - apologies, should have done a git pull.
In that case, just
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
Thanks for taking the lead on this patchset!
next prev parent reply other threads:[~2017-03-20 10:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 13:37 [dpdk-dev] [PATCH 0/2] add support for "unsupported testcases" in test framework Jerin Jacob
2017-03-19 13:37 ` [dpdk-dev] [PATCH 1/2] test: store only the test case name Jerin Jacob
2017-03-20 9:58 ` Van Haaren, Harry
2017-03-20 10:04 ` Jerin Jacob
2017-03-20 10:14 ` Van Haaren, Harry [this message]
2017-03-19 13:37 ` [dpdk-dev] [PATCH 2/2] test: add a new unit test case status Jerin Jacob
2017-03-20 9:58 ` Van Haaren, Harry
2017-03-27 9:07 ` [dpdk-dev] [PATCH 0/2] add support for "unsupported testcases" in test framework Thomas Monjalon
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=E923DB57A917B54B9182A2E928D00FA6129FE9C8@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=thomas.monjalon@6wind.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).