From: Bruce Richardson <bruce.richardson@intel.com>
To: "Laatz, Kevin" <kevin.laatz@intel.com>
Cc: "Van Haaren, Harry" <harry.van.haaren@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] meson: add tests app to build
Date: Wed, 20 Dec 2017 12:00:57 +0000 [thread overview]
Message-ID: <20171220120057.GB5200@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <17B8B96B619B7A459C5ACA628B274952819F0F@IRSMSX103.ger.corp.intel.com>
On Wed, Dec 20, 2017 at 11:57:59AM +0000, Laatz, Kevin wrote:
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Harry van Haaren
> > Sent: Wednesday, December 20, 2017 11:17 AM
> > To: dev@dpdk.org
> > Cc: Richardson, Bruce <bruce.richardson@intel.com>; Van Haaren, Harry
> > <harry.van.haaren@intel.com>
> > Subject: [dpdk-dev] [PATCH v2 2/2] meson: add tests app to build
>
> <snip>
>
> > +test_names = [
> > + 'acl_autotest',
> > + 'alarm_autotest',
> > + 'atomic_autotest',
> > + 'byteorder_autotest',
> > + 'cmdline_autotest',
> > + 'common_autotest',
> > + 'cpuflags_autotest',
> > + 'crc_autotest',
> > + 'cycles_autotest',
> > + 'debug_autotest',
> > + 'devargs_autotest',
> > + 'distributor_autotest',
> > + 'distributor_perf_autotest',
> > + 'eal_flags_autotest',
> > + 'eal_fs_autotest',
> > + 'efd_autotest',
> > + 'efd_perf_autotest',
> > + 'errno_autotest',
> > + 'event_ring_autotest',
> > + 'eventdev_common_autotest',
> > + 'eventdev_octeontx_autotest',
> > + 'eventdev_sw_autotest',
> > + 'func_reentrancy_autotest',
> > + 'has_scaling_autotest',
>
> Minor typo here, should be 'hash_scaling_autotest',
>
Good catch. I can fix on apply.
I'll also fix build error caused in this patch by the earlier applied
patch for cross-compile support. The build of the binary needs
"c_args: machine_arg" added to it following that change.
/Bruce
next prev parent reply other threads:[~2017-12-20 12:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 11:53 [dpdk-dev] [PATCH 0/2] next-build: add test " Harry van Haaren
2017-12-18 11:53 ` [dpdk-dev] [PATCH 1/2] test: use env variable to run test if set Harry van Haaren
2017-12-18 13:50 ` Bruce Richardson
2017-12-18 14:59 ` Jerin Jacob
2017-12-18 15:24 ` Van Haaren, Harry
2017-12-18 15:41 ` Jerin Jacob
2017-12-18 11:53 ` [dpdk-dev] [PATCH 2/2] meson: add tests app to build Harry van Haaren
2017-12-18 13:55 ` Bruce Richardson
2017-12-18 15:24 ` Van Haaren, Harry
2017-12-20 10:23 ` Bruce Richardson
2017-12-18 13:57 ` [dpdk-dev] [PATCH 0/2] next-build: add test " Bruce Richardson
2017-12-18 15:24 ` Van Haaren, Harry
2017-12-20 11:16 ` [dpdk-dev] [PATCH v2 " Harry van Haaren
2017-12-20 11:16 ` [dpdk-dev] [PATCH v2 1/2] test: use env variable to run test if set Harry van Haaren
2017-12-20 11:47 ` Bruce Richardson
2017-12-20 11:16 ` [dpdk-dev] [PATCH v2 2/2] meson: add tests app to build Harry van Haaren
2017-12-20 11:57 ` Laatz, Kevin
2017-12-20 12:00 ` Bruce Richardson [this message]
2017-12-20 12:20 ` Bruce Richardson
2017-12-20 12:22 ` [dpdk-dev] [PATCH v2 0/2] next-build: add test " Bruce Richardson
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=20171220120057.GB5200@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=kevin.laatz@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).