11 May
2015
11 May
'15
10:02 p.m.
On 05/11/2015 11:08 AM, Joe Hershberger wrote:
In order to reduce merge conflicts and to maintain the simplest possible defconfig files, we should be using the savedefconfig feature of Kconfig every time a new feature is added. This keeps the defconfig settings to a minimum (only those things not default) and keeps them in the same order as the Kconfig options.
diff --git a/configs/jetson-tk1_defconfig b/configs/jetson-tk1_defconfig
-CONFIG_TARGET_JETSON_TK1=y
Doesn't that (and the equivalent change in other files such as harmony_defconfig) break the build, since the Kconfig option that selects the particular board is no longer selected?