[OE-core] [PATCH 0/3] Make kernel-yocto bbclass usable without linux-yocto.inc

[Bruce Ashfield]

On Wed, Jan 15, 2020 at 1:36 PM Bruce Ashfield <bruce.ashfield at gmail.com> wrote:
>
> I already have an entire queue in development for this.
>
> So hold onto this series. I'll publish my branch later this week, or early next.

Actually, I'll see how it stacks on top of my changes and send a
unified branch to try out. That's probably the easiest way to get them
all working together.

Patches 2/3 look good, but I'd rather wait until we have the whole
series ready to go before Acking.

Cheers,

Bruce

>
> Bruce
>
> On Wed, Jan 15, 2020 at 1:08 PM Paul Barker <pbarker at konsulko.com> wrote:
> >
> > Patch 1 allows the kernel-yocto bbclass to be inherited directly in a recipe
> > without needing to use linux-yocto.inc. I can then use kconfig fragments in
> > my kernel recipe without pulling in the whole of linux-yocto.inc (which
> > includes some things I don't want like KERNEL_FEATURES changes and the
> > LINUX_VERSION_EXTENSION default).
> >
> > Patches 2 & 3 fix some minor issues I spotted while working on this.
> >
> > I've tested that linux-yocto can still be built for qemux86 after these
> > changes.
> >
> > Paul Barker (3):
> >   kernel-yocto: Move defaults and tasks from linux-yocto.inc into
> >     bbclass
> >   kernel-yocto: Drop setting of unused variables in do_kernel_metadata
> >   kernel-yocto: Only override CONFIG_LOCALVERSION if
> >     LINUX_VERSION_EXTENSION is set
> >
> >  meta/classes/kernel-yocto.bbclass         | 34 +++++++++++++++++------
> >  meta/recipes-kernel/linux/linux-yocto.inc | 21 --------------
> >  2 files changed, 25 insertions(+), 30 deletions(-)
> >
> > --
> > 2.20.1
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II



--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II