Hi Michal, On Tue, Mar 11, 2014 at 10:38:14AM +0100, Michal Simek wrote: > On 03/11/2014 05:45 AM, Fengguang Wu wrote: > >>> You probably want something like > >>> > >>> config CAN_XILINX > >>> tristate "Xilinx CAN" > >>> depends on ARCH_ZYNQ || MICROBLAZE || COMPILE_TEST > >>> depends on COMMON_CLK && HAS_MMIO # whatever you need for other > >>> architectures > >> > >> Fengguang: Are you use COMPILE_TEST in zero day testing system? > > > > Yeah, the randconfig build/boot tests should cover both COMPILE_TEST > > and !COMPILE_TEST cases. > > But the point is that randconfig is really random it means it definitely can > cover but not there is no certainty that for that build, you are running, > has both option for all architectures enabled. > Or do I read it wrongly?
Good point! Since the 0day system is running randconfig tests everyday, it has very good opportunity to cover the COMPILE_TEST case. But to be sure, I'll explicitly enable COMPILE_TEST in some cases. Thanks, Fengguang -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
