[meta-intel] [PATCHv2 1/2] meta-intel/common: Initial Intel DPDK recipe under recipes-extended

[Burton, Ross]

On 10 July 2014 09:40,  <wei.sern.chan at intel.com> wrote:
> +++ b/common/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-app-test-fix-build-switches-to-enable-cmdline-tests.patch
> @@ -0,0 +1,49 @@
> +From cf953d2bfa7df9aa67459b333db4d4d8a9e72fd6 Mon Sep 17 00:00:00 2001
> +From: Thomas Monjalon <thomas.monjalon at 6wind.com>
> +Date: Fri, 27 Jun 2014 11:21:11 +0200
> +Subject: [PATCH] app/test: fix build switches to enable cmdline tests
> +
> +There were 2 typos since these commits (in 1.6.0 releases):
> +       21a7f4e264 fix build without librte_cmdline
> +       cac6d08c8b replace --use-device option by --pci-whitelist and --vdev
> +In makefiles, the build options are prefixed with CONFIG_RTE_
> +but in .c file, it is only RTE_.
> +
> +These typos were disabling cmdline unit tests and test of "--vdev eth_ring" option.
> +
> +Signed-off-by: Thomas Monjalon <thomas.monjalon at 6wind.com>
> +Acked-by: Pablo de Lara <pablo.de.lara.guarch at intel.com>

Patches need to have a Signed-Off-By (presumably, you) and
Upstream-Status (in this case, Backport) at the top.  This is so we
know who is responsible for bringing the patch into oe-core, and that
as a backport its likely to be removed in the future.

> +# Recipe Ingredients (source, patch, etc)

Pointless comment.

> +export INSTALL_PATH = "${prefix}/dpdk"

Urgh, if it can't be told to install into $datadir $libdir etc, then that's sad.

Ross