Anas Nashif c47769bd56 kconfig: move all defconfig fragments to configs/ ... When building for a certain platform, we have no idea what architecture we are building for. We used to specify the architecture alongside the board or platform name and this was used to find the defconfig in arch/<arch>/configs. By putting all board configurations we support in one place we do not have to specify the architecture, just the configuration name. Change-Id: Ib7e9f63b9a8051714dc207f583fd26ef620497d8 Signed-off-by: Anas Nashif <anas.nashif@intel.com>		2016-02-05 20:24:53 -05:00
..
arduino_101_defconfig	kconfig: move all defconfig fragments to configs/	2016-02-05 20:24:53 -05:00
basic_atom_defconfig	kconfig: move all defconfig fragments to configs/	2016-02-05 20:24:53 -05:00
basic_cortex_m3_defconfig	kconfig: move all defconfig fragments to configs/	2016-02-05 20:24:53 -05:00
basic_minuteia_defconfig	kconfig: move all defconfig fragments to configs/	2016-02-05 20:24:53 -05:00
fsl_frdm_k64f_defconfig	kconfig: move all defconfig fragments to configs/	2016-02-05 20:24:53 -05:00
galileo_defconfig	kconfig: move all defconfig fragments to configs/	2016-02-05 20:24:53 -05:00
generic_arc_defconfig	kconfig: move all defconfig fragments to configs/	2016-02-05 20:24:53 -05:00
quark_d2000_defconfig	kconfig: move all defconfig fragments to configs/	2016-02-05 20:24:53 -05:00
quark_se-arc_defconfig	kconfig: move all defconfig fragments to configs/	2016-02-05 20:24:53 -05:00
quark_se-x86_defconfig	kconfig: move all defconfig fragments to configs/	2016-02-05 20:24:53 -05:00