diff options
author | Andrew Geissler <geissonator@yahoo.com> | 2020-09-01 18:25:32 +0300 |
---|---|---|
committer | Andrew Geissler <geissonator@yahoo.com> | 2020-09-01 22:09:43 +0300 |
commit | 32cc5c1f5be9b95ed6ae62eb76f5f06afbd18805 (patch) | |
tree | 33e0b2e9c0a458092d103efc1ea619c51b9009a6 /meta-qualcomm | |
parent | 1ee6bb5418787ac573e6f6edaccc99cfd11edeea (diff) | |
download | openbmc-32cc5c1f5be9b95ed6ae62eb76f5f06afbd18805.tar.xz |
nuvoton: enable KERNEL_DANGLING_FEATURES_WARN_ONLY
Uptream yocto recently added some new code which enforces
kernel feature validation. The commit which did this is:
https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=095175595d9f28d5a0eb7ea520c9af0100bb8dfd
This caused OpenBMC builds to start failing with the following:
| ERROR: Feature 'phosphor-gpio-keys' not found, this will cause configuration failures.
| ERROR: Check the SRC_URI for meta-data repositories or directories that may be missing
| ERROR: Set KERNEL_DANGLING_FEATURES_WARN_ONLY to ignore this issue
OpenBMC does not utilize this aspect of the kernel-yocto.bbclass
so make it a warning only.
Tested:
Verified that the resultant build still had the expected CONFIG
options set in the linux-nuvoton .config file
See openbmc/openbmc#3690
(From meta-phosphor rev: 75a6424eec93729fd40154413b1a350b9f10fe8b)
Change-Id: I12bf3857601f186300d3b1c56c490be6e6582dda
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to 'meta-qualcomm')
0 files changed, 0 insertions, 0 deletions