On Mon, Jun 17, 2019 at 6:04 PM Alistair Francis <[email protected]> wrote: > > Signed-off-by: Alistair Francis <[email protected]> > --- > meta/recipes-kernel/linux/linux-yocto_5.0.bb | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb > b/meta/recipes-kernel/linux/linux-yocto_5.0.bb > index 8aec315084..a79d0b962d 100644 > --- a/meta/recipes-kernel/linux/linux-yocto_5.0.bb > +++ b/meta/recipes-kernel/linux/linux-yocto_5.0.bb > @@ -41,7 +41,7 @@ KCONF_BSP_AUDIT_LEVEL = "2" > KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb" > KERNEL_DEVICETREE_qemuarmv5 = "versatile-pb.dtb" > > -COMPATIBLE_MACHINE = > "qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64" > +COMPATIBLE_MACHINE = > "qemuarm|qemuarmv5|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemuriscv64"
What KBRANCH / SRCREV would this be building ? Unless it is something that I'm building and booting, we shouldn't put it in the core recipe as compatible until the SRCREV and KBRANCH are defined. Bruce > > # Functionality flags > KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc" > -- > 2.22.0 > > -- > _______________________________________________ > Openembedded-core mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
