Re: [meta-arm][PATCH] optee-os: Mark recipes dormant by default

["Denys Dmytriyenko" <denis@denix.org>]

On Mon, Apr 13, 2020 at 06:06:37PM -0400, Denys Dmytriyenko wrote:
> On Mon, Apr 13, 2020 at 06:05:19PM -0400, Jon Mason wrote:
> > On Sat, Apr 11, 2020 at 10:45:31PM -0700, Khem Raj wrote:
> > > all arm SOCs may not support optee and there are non-arm machines too
> > > this makes this recipe fit into mutli-BSP environments, platforms which
> > > support optee should be specifically called out via COMPATIBLE_MACHINE,
> > > for general case it remains 'null'
> > 
> > Pulled into the master branch.
> 
> I think this was due to the parsing issues, resolved by another patch. What's 
> the point of masking this recipes now?
> 
> 
> > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > > ---
> > >  
> > > diff --git a/meta-arm/recipes-security/optee/optee.inc b/meta-arm/recipes-security/optee/optee.inc
> > > new file mode 100644
> > > index 0000000..a12521d
> > > --- /dev/null
> > > +++ b/meta-arm/recipes-security/optee/optee.inc
> > > @@ -0,0 +1,2 @@
> > > +COMPATIBLE_MACHINE = "null"
> > > +# Please add supported machines below

Can we instead of neutering all OPTEE recipes and requiring BSPs to provide 
bbappends with COMPATIBLE_MACHINE for opt-in, add EXCLUDE_FROM_WORLD = "1"?

-- 
Denys