diff options
author | Bruce Ashfield <bruce.ashfield@windriver.com> | 2013-02-16 04:32:38 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-03-02 22:43:06 +0000 |
commit | faf042b2c87874153a6b689479ab86e49804af8c (patch) | |
tree | 93a629658c959515be34d6f73fabfd2e6351f2e3 | |
parent | f0c600ce8971c5444198ffe4f596b671e3e668cf (diff) | |
download | openembedded-core-faf042b2c87874153a6b689479ab86e49804af8c.tar.gz openembedded-core-faf042b2c87874153a6b689479ab86e49804af8c.tar.bz2 openembedded-core-faf042b2c87874153a6b689479ab86e49804af8c.zip |
kern-tools: import configuration, controls and audit updates
Updating the kern-tools SRCREV to import the following fixes:
commit 7f91d198d32fc90260e52724ef4aac0b997c1e8b
kconf_check: fix new Kconfig detection
One of the functions of the kernel configuration audit is to notify
the user if Kconfig* files have been removed from the kernel, and
also to notify of new Kconfig files.
New Kconfig files should be classified as hardware or non-hardware to
allow BSP audits to notify if boards are setting values that they
shouldn't, hence why notifying about new "buckets" is important.
commit c4f26a3296e0e1c3dbdd5ec8e2947d5443a9ffc2
updateme/scc: allow config fragment exclusion
It is common to need the features (patches, git operations) of a
branch, but not want the kernel configuration fragments of a given
branch. To allow this, we provide a new include flag "nocfg".
When this flag is used, all of the configuration fragments included
by the targetted feature will not be applied to the current build,
with one exception, a base/critical fragment can force it's config
values, since without them, the system would not be functional.
Example:
include ktypes/standard/standard.scc nocfg
commit c7ec19d55aca6c4b17073c5362fce5be61a89d82
scc: wrap git merge
To allow for parameter validation and sanity checking, wrap "git merge"
as a dedicated "merge" command instead of using the raw git fallback.
This also makes it consistent with existing top level commands such
as 'tag', 'branch', 'patch', etc.
There are no changes to arguments, and existing 'git merge' commands
continue to work with this change.
[YOCTO #3419]
[YOCTO #3421]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r-- | meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb index 98cd8b9e85..9f4438c119 100644 --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70c DEPENDS = "git-native guilt-native" -SRCREV = "9284af9b968d40e441b10f5c09961cbe329ccb9b" +SRCREV = "7f91d198d32fc90260e52724ef4aac0b997c1e8b" PR = "r12" PV = "0.1+git${SRCPV}" |