Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Armin Kuster" <akuster808@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/2] kernel-kfrag: add new class
Date: Sun, 30 May 2021 13:54:48 -0700	[thread overview]
Message-ID: <9bc2b2eb-7691-82a2-e68f-8b9d6c7459ce@gmail.com> (raw)
In-Reply-To: <CADkTA4ORQc2j9W9QgRJUhDY=q1ZLUdKxctJj=HLdkPPm9iGoTA@mail.gmail.com>



On 5/30/21 1:47 PM, Bruce Ashfield wrote:
> On Sun, May 30, 2021 at 2:06 PM Armin Kuster <akuster808@gmail.com> wrote:
>> This provides a common place to define kernel fragments
>> that may be usefull to the larger community.
> Not a bad idea at all, but what about calling the class
> "kernel-features", versus kfrag ? That describes the purpose, versus
> what the mechanism does.
works for me.
>
> A 2nd suggestion would be to bbwarn if this is inherited, but
> kernel-yocto is not.
seems reasonable.  I did wonder the best place to place for thie. The
kernel cache can be used w/o linux-yocto.
>
> Note: as mentioned during the yocto summit, I do have patches that
> make fragments more universally available, when I get them ready, we
> could remove the bbwarn.
Would those patches eliminate the need for a class like this?

-armin
>
> Bruce
>
>> Signed-off-by: Armin Kuster <akuster808@gmail.com>
>> ---
>>  meta/classes/kernel-kfrag.bbclass | 8 ++++++++
>>  1 file changed, 8 insertions(+)
>>  create mode 100644 meta/classes/kernel-kfrag.bbclass
>>
>> diff --git a/meta/classes/kernel-kfrag.bbclass b/meta/classes/kernel-kfrag.bbclass
>> new file mode 100644
>> index 00000000000..c0c5667b519
>> --- /dev/null
>> +++ b/meta/classes/kernel-kfrag.bbclass
>> @@ -0,0 +1,8 @@
>> +#
>> +# Class to place yocto-kernel-cache fragments
>> +# selections usfull to anyone
>> +#
>> +
>> +KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "apparmor", " features/apparmor/apparmor.scc", "" ,d)}"
>> +KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "smack", " features/smack/smack.scc", "" ,d)}"
>> +KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "dm-verity", " features/device-mapper/dm-verity.scc", "" ,d)}"
>> --
>> 2.24.3
>>
>>
>> 
>>
>


  reply	other threads:[~2021-05-30 20:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-30 18:05 [PATCH 1/2] kernel-kfrag: add new class Armin Kuster
2021-05-30 18:05 ` [PATCH 2/2] kernel.bbclass: include kernel-kfrag Armin Kuster
2021-05-30 20:47 ` [OE-core] [PATCH 1/2] kernel-kfrag: add new class Bruce Ashfield
2021-05-30 20:54   ` Armin Kuster [this message]
2021-05-31  2:27     ` Bruce Ashfield

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9bc2b2eb-7691-82a2-e68f-8b9d6c7459ce@gmail.com \
    --to=akuster808@gmail.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox