On 08.03.2023 11:49, Michal Orzel wrote: > Despite being a matter of taste, in general, there are two main approaches > when dealing with code tagging: tree-wide, where all the sources are taken > into account or config-wide, when considering Kconfig options and actually > built files. At the moment, all_sources variable is defined using SUBDIRS, > which lists all the directories except arch/, where only $(TARGET_ARCH) > is taken into account. This makes it difficult to reason about and creates > fuzzy boundaries being a blocker when considering new directories that > might be config-dependent (like crypto/ which is missing in SUBDIRS). > > For now, switch to the intermediate solution to list all the directories > in SUBDIRS without exceptions (also include crypto/). This way, the > approach taken is clear allowing new directories to be listed right away > without waiting to fix the infrastructure first. In the future, we can > then add support for config-wide approach. > > Signed-off-by: Michal Orzel <[email protected]>
Acked-by: Jan Beulich <[email protected]>
