Having standard follow ktypes/preempt-rt/preempt-rt.scc means that settings in standard take precedence, which isn't the expected behavior.
Signed-off-by: Tom Zanussi <tom.zanu...@linux.intel.com> --- meta/cfg/kernel-cache/bsp/intel-common/intel-corei7-64-preempt-rt.scc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/cfg/kernel-cache/bsp/intel-common/intel-corei7-64-preempt-rt.scc b/meta/cfg/kernel-cache/bsp/intel-common/intel-corei7-64-preempt-rt.scc index d020408..d5bed76 100644 --- a/meta/cfg/kernel-cache/bsp/intel-common/intel-corei7-64-preempt-rt.scc +++ b/meta/cfg/kernel-cache/bsp/intel-common/intel-corei7-64-preempt-rt.scc @@ -2,8 +2,9 @@ define KMACHINE intel-corei7-64 define KTYPE preempt-rt define KARCH x86_64 +include intel-common-standard.scc + # no new branch required, re-use the ktypes/preempt-rt/preempt-rt.scc branch include ktypes/preempt-rt/preempt-rt.scc -include intel-common-standard.scc include intel-corei7-64.scc -- 1.8.3.1 -- _______________________________________________ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
