From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: pablo.de.lara.guarch@intel.com, dev@dpdk.org
Subject: Re: [PATCH v2 0/4] improve build coverage
Date: Thu, 06 Apr 2017 21:45:14 +0200 [thread overview]
Message-ID: <2478653.9mtuBhKHMk@xps13> (raw)
In-Reply-To: <20170329163856.10932-1-bruce.richardson@intel.com>
2017-03-29 17:38, Bruce Richardson:
> This patch aims to increase the amount of code coverage we get when
> doing a basic build of DPDK using the build tools and scripts. It does this
> by enabling in our makefiles and default build configuration extra drivers
> and examples which don't have extra external requirements. It then adjusts
> the testbuild script to ensure it covers the test binary which was recently
> removed from the default build.
>
> V2: corrected test-build additions for the autotest binary, since
> test-build skips testpmd and the other apps. Therefore we need to run two
> build commands to build everything.
>
> Bruce Richardson (4):
> examples: enable performance-thread in examples build
> config: enable crypto scheduler PMD by default
> devtools: remove special case build for perf thread example
> devtools: add autotest app to build script
Applied with suggested modifications, thanks
prev parent reply other threads:[~2017-04-06 19:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 14:04 [PATCH 0/4] improve build coverage Bruce Richardson
2017-03-29 14:04 ` [PATCH 1/4] examples: enable performance-thread in examples build Bruce Richardson
2017-03-29 14:04 ` [PATCH 2/4] config: enable crypto scheduler PMD by default Bruce Richardson
2017-03-30 14:48 ` Zhang, Roy Fan
2017-03-29 14:04 ` [PATCH 3/4] devtools: remove special case build for perf thread example Bruce Richardson
2017-03-29 14:04 ` [PATCH 4/4] devtools: add autotest app to build script Bruce Richardson
2017-03-29 16:38 ` [PATCH v2 0/4] improve build coverage Bruce Richardson
2017-03-29 16:38 ` [PATCH v2 1/4] examples: enable performance-thread in examples build Bruce Richardson
2017-03-30 7:45 ` Declan Doherty
2017-03-29 16:38 ` [PATCH v2 2/4] config: enable crypto scheduler PMD by default Bruce Richardson
2017-03-30 7:45 ` Declan Doherty
2017-03-29 16:38 ` [PATCH v2 3/4] devtools: remove special case build for perf thread example Bruce Richardson
2017-03-30 7:46 ` Declan Doherty
2017-03-30 14:31 ` Thomas Monjalon
2017-03-30 15:30 ` Bruce Richardson
2017-03-30 20:38 ` Thomas Monjalon
2017-03-31 9:15 ` Bruce Richardson
2017-03-31 9:56 ` Thomas Monjalon
2017-03-29 16:38 ` [PATCH v2 4/4] devtools: add autotest app to build script Bruce Richardson
2017-03-30 7:47 ` Declan Doherty
2017-03-30 14:36 ` Thomas Monjalon
2017-03-30 15:33 ` Bruce Richardson
2017-03-30 20:42 ` Thomas Monjalon
2017-04-04 13:03 ` Ferruh Yigit
2017-04-06 19:45 ` Thomas Monjalon [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=2478653.9mtuBhKHMk@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.