On 12/26, [email protected] wrote: > From: Sean Wang <[email protected]> > > commit 74cb0d6dde8 ("clk: mediatek: fixup test-building of MediaTek clock > drivers") can let the build system looking into the directory where the > clock drivers resides and then allow test-building the drivers. > > But the change also gives rise to certain incorrect behavior which is > reset.c being built even not depending on either COMPILE_TEST or > ARCH_MEDIATEK alternative dependency. To get rid of reset.c being built > unexpectedly on the other platforms, it would be a good change that the > file should be built depending on its own specific configuration rather > than just on generic RESET_CONTROLLER one. > > Signed-off-by: Sean Wang <[email protected]> > Cc: Jean Delvare <[email protected]>
I've typically seen vendor Kconfigs select the RESET_CONTROLLER framework if the vendor Kconfig is enabled. Any reason that same method isn't followed here? -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
