[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140313112112.GB8806@localhost>
Date: Thu, 13 Mar 2014 19:21:12 +0800
From: Fengguang Wu <fengguang.wu@...el.com>
To: Michal Simek <michal.simek@...inx.com>
Cc: Arnd Bergmann <arnd@...db.de>,
linux-arm-kernel@...ts.infradead.org,
Marc Kleine-Budde <mkl@...gutronix.de>, monstr@...str.eu,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, linux-can@...r.kernel.org,
robh+dt@...nel.org,
Kedareswara rao Appana <appana.durga.rao@...inx.com>,
grant.likely@...aro.org,
Kedareswara rao Appana <appanad@...inx.com>,
wg@...ndegger.com
Subject: Re: [PATCH v5] can: xilinx CAN controller support.
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 netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists