Le 24/01/2018 à 15:00, Adam Ford a écrit :
Many boards are setting NAND parameters if/when CMD_NAND is set when in reality they should probably be doing it it CONFIG_NAND is set. Previuos attempts to make CMD_NAND select CONFIG_NAND resulted in some recursive selections, so I think this should be a better solution
Using the moveconfig tool, I searched for CONFIG_SYS_MAX_NAND_DEVICE and then any suspicious defconfig files left behind, I added CONFIG_NAND=y, then retested the migration against that list.
This should allows us to make the CONFIG_CMD_NAND now dependant on CONFIG_NAND and enable a bunch of NAND parameters under the NAND menu without appearing 'suspicious'
This converts the following to Kconfig: CONFIG_SYS_MAX_NAND_DEVICE
Signed-off-by: Adam Ford aford173@gmail.com
configs/MCR3000_defconfig | 1 + include/configs/MCR3000.h | 1 -
For the two above files:
Acked-by: christophe.leroy@c-s.fr