[OE-core] [RFC PATCH 1/6] classes/kernel-check: add a class to check kernel config options

Bruce Ashfield bruce.ashfield at gmail.com
Mon May 9 21:00:26 UTC 2016


On Mon, May 9, 2016 at 4:53 PM, Paul Eggleton <paul.eggleton at linux.intel.com
> wrote:

> On Mon, 09 May 2016 07:59:43 Bruce Ashfield wrote:
> > On Mon, May 9, 2016 at 12:43 AM, Paul Eggleton <
> > paul.eggleton at linux.intel.com> wrote:
> > > Some user-space software has specific requirements about the kernel
> > > configuration options selected. This class allows a recipe to
> explicitly
> > > state the kernel configuration options it needs (through a
> > > REQUIRED_KERNEL_OPTIONS variable). This is a space separated list,
> where
> > >
> > > each item is one of:
> > >   (a) an option name (e.g. CONFIG_FHANDLE, in which case CONFIG_FHANDLE
> > >
> > >       must be set to y or m to match)
> > >
> > >   (b) optionname=value (e.g. CONFIG_FHANDLE=y, in which case
> > >
> > >       CONFIG_FHANDLE must be set to y). If the specified value is n,
> > >       it will also match if the option is not present.
> > >
> > >   (c) optionname1|optionname2|... (e.g.
> > >
> > >       CONFIG_EXT2_FS|CONFIG_EXT4_USE_FOR_EXT23, meaning that either
> > >       CONFIG_EXT2_FS or CONFIG_EXT4_USE_FOR_EXT23 must be set to y or
> > >       m to match).
> >
> > This duplicates code that is already in the kconf_check routines, which
> > I've already made generic (and added dependency information) for the 2.2
> > release ... so call me confused that I've never heard about this until
> now
> > :(
>
> I guess I didn't look hard enough, I'll have to take a look at that. This
> is
> why the series is RFC (and I included you on CC ;)
>

Noted :) I read the patches before the 0/N .. and it was Monday morning
before coffee.

Don't look TOO closely as your eyes will bleed, but the basics are there.
My recent
work has been to clean it up so I can apply it to an arbitrary kernel.

Bruce


>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160509/b1a07dcf/attachment-0002.html>


More information about the Openembedded-core mailing list