-
Notifications
You must be signed in to change notification settings - Fork 153
Include qcom.config in KBUILD_CONFIG_EXTRA of linux-qcom-next recipe #1250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -37,7 +37,8 @@ KBUILD_DEFCONFIG ?= "defconfig" | |
| KBUILD_DEFCONFIG:qcom-armv7a = "qcom_defconfig" | ||
|
|
||
| KBUILD_CONFIG_EXTRA = "${@bb.utils.contains('DISTRO_FEATURES', 'hardened', '${S}/kernel/configs/hardening.config', '', d)}" | ||
| KBUILD_CONFIG_EXTRA:append:aarch64 = "${S}/arch/arm64/configs/prune.config" | ||
| KBUILD_CONFIG_EXTRA:append:aarch64 = " ${S}/arch/arm64/configs/prune.config" | ||
| KBUILD_CONFIG_EXTRA:append:aarch64 = " ${S}/arch/arm64/configs/qcom.config" | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is provided by the kernel tree, but we also have a qcom.cfg fragment (and now qcom.config), not an issue necessarily but might cause confusion later on (what is in tree and what is provided by the recipe).
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The in-tree |
||
|
|
||
| do_configure:prepend() { | ||
| # Use a copy of the 'defconfig' from the actual repo to merge fragments | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.