Message ID | 20220513184201.2517163-1-ross.burton@arm.com |
---|---|
State | Accepted, archived |
Commit | c807876507fa0257be9abc15457b312e01368c17 |
Headers | show |
Series | kernel-yocto.bbclass: say what SRC_URI entry is being dropped | expand |
diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass index fb30c7cc055..b276ded7751 100644 --- a/meta/classes/kernel-yocto.bbclass +++ b/meta/classes/kernel-yocto.bbclass @@ -192,7 +192,7 @@ do_kernel_metadata() { if [ -n "$in_tree_defconfig" ]; then sccs_defconfig=$in_tree_defconfig if [ -n "$src_uri_defconfig" ]; then - bbwarn "[NOTE]: defconfig was supplied both via KBUILD_DEFCONFIG and SRC_URI. Dropping SRC_URI defconfig" + bbwarn "[NOTE]: defconfig was supplied both via KBUILD_DEFCONFIG and SRC_URI. Dropping SRC_URI entry $src_uri_defconfig" fi else # if we didn't have an in-tree one, make our defconfig the one
If there is a defconfig set by KBUILD_DEFCONFIG and something that looks like a defconfig in SRC_URI, the SRC_URI is dropped. This happens even if the entry in SRC_URI is called my_defconfig_frag.cfg. Arguably, this is a bug and the behaviour should be changed, but for now if we're going to remove entries from SRC_URI we should make it clear what entry is being removed. Signed-off-by: Ross Burton <ross.burton@arm.com> --- meta/classes/kernel-yocto.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)