-
Notifications
You must be signed in to change notification settings - Fork 135
Add kernel config fragment for custom Linux kernel recipe #1125
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?
Conversation
dda3068
to
b9b4d22
Compare
Github doesn't seem to allow including the commit message in reviews, so:
The commit policy is "Recipe: change", so change it to something like "linux-qcom-next: add support for KERNEL_CONFIG_FRAGMENTS"
That's not your name |
6f0f1ba
to
c0d7a33
Compare
KBUILD_DEFCONFIG ?= "defconfig" | ||
KBUILD_DEFCONFIG:qcom-armv7a = "qcom_defconfig" | ||
|
||
KERNEL_CONFIG_FRAGMENTS = " ${UNPACKDIR}/configs/qcom.cfg" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need for the whitespace
Certain kernel features, require specific kernel configuration options that are not present in the default configuration. Introducing kernel config fragment support to explicitly define required configuration for custom features. Signed-off-by: Ravi Kumar Siddojigari <[email protected]>
KBUILD_DEFCONFIG ?= "defconfig" | ||
KBUILD_DEFCONFIG:qcom-armv7a = "qcom_defconfig" | ||
|
||
KERNEL_CONFIG_FRAGMENTS = "${UNPACKDIR}/configs/qcom.cfg" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's not clear how we intend to use this new variable. especially because it's initialized without =?
Add kernel config fragment support for custom Linux kernel recipe.