From: Paul Barker <pbarker@konsulko.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Make kernel-yocto bbclass usable without linux-yocto.inc
Date: Wed, 15 Jan 2020 18:08:25 +0000 [thread overview]
Message-ID: <20200115180828.17399-1-pbarker@konsulko.com> (raw)
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
next reply other threads:[~2020-01-15 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 18:08 Paul Barker [this message]
2020-01-15 18:08 ` [PATCH 1/3] kernel-yocto: Move defaults and tasks from linux-yocto.inc into bbclass Paul Barker
2020-01-15 18:08 ` [PATCH 2/3] kernel-yocto: Drop setting of unused variables in do_kernel_metadata Paul Barker
2020-01-15 18:08 ` [PATCH 3/3] kernel-yocto: Only override CONFIG_LOCALVERSION if LINUX_VERSION_EXTENSION is set Paul Barker
2020-01-15 18:36 ` [PATCH 0/3] Make kernel-yocto bbclass usable without linux-yocto.inc Bruce Ashfield
2020-01-15 18:46 ` Bruce Ashfield
2020-01-24 23:14 ` 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=20200115180828.17399-1-pbarker@konsulko.com \
--to=pbarker@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.