2bd07a47f9
For targets that uses mainline kernel, the kernel tree usually only
contains configs on top of the upstream repository.
In such case, if we put the configs in elsewhere, we can simply just
track the upstream kernel repo, without needing to import configs.
Example usage:
TARGET_KERNEL_CONFIG_EXT := \
$(COMMON_PATH)/kconfig/platform_defconfig \
$(COMMON_PATH)/kconfig/common-addons.config
TARGET_KERNEL_CONFIG_EXT += \
$(DEVICE_PATH)/kconfig/device.config
Change-Id: Ibafd0afa7ec06df643ba290a6149a4f0781d67fb
LineageOS =========== Getting started --------------- Please see the [LineageOS Wiki](https://wiki.lineageos.org/) for building instructions, by device. Submitting patches ------------------ Patches are always welcome! Please submit your patches via LineageOS Gerrit! Simply follow our guide on [how to submit patches](https://wiki.lineageos.org/submitting-patch-howto.html). To view the status of your and others' patches, visit [LineageOS Gerrit Code Review](https://review.lineageos.org/). Buildbot -------- All supported devices are built weekly and periodically as changes are committed to ensure the source trees remain buildable. You can view the current build statuses at [LineageOS Buildkite](https://buildkite.com/lineageos). Builds produced weekly by the buildbot can be downloaded from [LineageOS downloads](https://download.lineageos.org/).