From: "Franklin S. Cooper Jr" <[email protected]> * Avoid creating a "new" defconfig when the one used by the recipe gives the same exact result. * This also avoids the confusion people have when seeing a defconfig that doesn't exist in any other git tree. * Doing this only makes sense if the defconfig is intree and not being patched.
Signed-off-by: Franklin S. Cooper Jr <[email protected]> --- .../linux/sitara-linux-ti-staging_3.14.bbappend | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/meta-arago-distro/recipes-kernel/linux/sitara-linux-ti-staging_3.14.bbappend b/meta-arago-distro/recipes-kernel/linux/sitara-linux-ti-staging_3.14.bbappend index b0b1df2..7e8eaf2 100644 --- a/meta-arago-distro/recipes-kernel/linux/sitara-linux-ti-staging_3.14.bbappend +++ b/meta-arago-distro/recipes-kernel/linux/sitara-linux-ti-staging_3.14.bbappend @@ -1,9 +1,7 @@ -MACHINE_KERNEL_PR_append = "-arago0" +MACHINE_KERNEL_PR_append = "-arago1" FILESEXTRAPATHS_prepend := "${THISDIR}/${P}:" -require copy-defconfig.inc - KERNEL_LOCALVERSION = "-g${@d.getVar('SRCPV', True).partition('+')[2][0:7]}" kernel_do_configure_prepend() { -- 1.7.9.5 _______________________________________________ meta-arago mailing list [email protected] http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
