On Thu Dec 4, 2025 at 7:43 PM CET, Andrew Davis wrote: > On 12/4/25 4:25 AM, Markus Schneider-Pargmann (TI.com) wrote: >> Much of the config symbols between the evm boards are the same >> independent of the actual board. This patch creates a hierarchy for the >> am335x_evm configs: >> >> am335x_evm.config >> `-> am335x_evm_defconfig >> `-> am335x_evm_spiboot_defconfig >> `-> am335x_hs_evm.config >> `-> am335x_hs_evm_defconfig >> `-> am335x_hs_evm_uart_defconfig >> > > Idea looks good to me, but why not have am335x_evm_defconfig be the top > of the hierarchy instead of a new file? Same for HS, so something like this: > > am335x_evm_defconfig > `-> am335x_evm_spiboot_defconfig > `-> am335x_hs_evm_defconfig > `-> am335x_hs_evm_uart_defconfig
Yes, I would like to do that as well (and tried), but there are symbols set in am335x_evm_defconfig that are not set in am335x_hs_evm_defconfig for example. If I remove that symbol like this: # CONFIG_... is not set 'make am335x_hs_evm_defconfig' will complain: generated_defconfig:87:warning: override: reassigning to symbol CONFIG_... I don't know how to get rid of that warning without the additional files I introduced. Best Markus
signature.asc
Description: PGP signature
