From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Bruce Ashfield <bruce.ashfield@windriver.com>,
Tom Zanussi <tom.zanussi@intel.com>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: [RFC PATCH 0/6] Kernel configuration check for recipes
Date: Mon, 9 May 2016 16:43:26 +1200 [thread overview]
Message-ID: <cover.1462768634.git.paul.eggleton@linux.intel.com> (raw)
Add the capability for other recipes to verify that kernel
configuration options they depend upon at runtime are present, and warn
if they are missing. This seems functional enough to me but is still in
RFC - please let me know if it looks OK to you or I've missed anything
(no doubt there are recipes we could add the checks to, I refer mainly
to the mechanism itself).
Please review the following changes for suitability for inclusion. If you have
any objections or suggestions for improvement, please respond to the patches. If
you agree with the changes, please provide your Acked-by.
The following changes since commit ece101be5158beee709cdfbb85ecdbdc8d9fb864:
test-empty-image: Fix LIC_FILES_CHKSUM typo (2016-05-06 10:47:59 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/kernel-check
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/kernel-check
Paul Eggleton (6):
classes/kernel-check: add a class to check kernel config options
eudev: check for required kernel config options
systemd: check for required kernel config options
classes/kernel: fix typo
classes/kernel: check OLDEST_KERNEL at configure time
classes/image: check kernel config supports IMAGE_FSTYPES items
meta/classes/image.bbclass | 23 ++++++++
meta/classes/image_types.bbclass | 11 ++++
meta/classes/kernel-check.bbclass | 97 ++++++++++++++++++++++++++++++++
meta/classes/kernel.bbclass | 16 +++++-
meta/recipes-core/systemd/systemd_229.bb | 19 ++++++-
meta/recipes-core/udev/eudev_3.1.5.bb | 22 +++++++-
6 files changed, 185 insertions(+), 3 deletions(-)
create mode 100644 meta/classes/kernel-check.bbclass
--
2.5.5
next reply other threads:[~2016-05-09 4:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 4:43 Paul Eggleton [this message]
2016-05-09 4:43 ` [RFC PATCH 1/6] classes/kernel-check: add a class to check kernel config options Paul Eggleton
2016-05-09 11:59 ` Bruce Ashfield
2016-05-09 20:53 ` Paul Eggleton
2016-05-09 21:00 ` Bruce Ashfield
2016-05-09 4:43 ` [RFC PATCH 2/6] eudev: check for required " Paul Eggleton
2016-05-09 4:43 ` [RFC PATCH 3/6] systemd: " Paul Eggleton
2016-05-10 0:31 ` Khem Raj
2016-05-09 4:43 ` [RFC PATCH 4/6] classes/kernel: fix typo Paul Eggleton
2016-05-09 4:43 ` [RFC PATCH 5/6] classes/kernel: check OLDEST_KERNEL at configure time Paul Eggleton
2016-05-10 0:33 ` Khem Raj
2016-05-09 4:43 ` [RFC PATCH 6/6] classes/image: check kernel config supports IMAGE_FSTYPES items Paul Eggleton
2016-05-09 12:05 ` Bruce Ashfield
2016-05-09 16:57 ` Christopher Larson
2016-05-09 19:35 ` Bruce Ashfield
2016-05-09 20:45 ` Paul Eggleton
2016-05-09 20:58 ` Bruce Ashfield
2016-05-09 12:08 ` [RFC PATCH 0/6] Kernel configuration check for recipes Bruce Ashfield
2016-05-09 20:55 ` Paul Eggleton
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=cover.1462768634.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=tom.zanussi@intel.com \
/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