[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <546dbc60-dd7b-4249-bab8-ad7e008b9aad@AM1EHSMHS001.ehs.local>
Date: Tue, 11 Mar 2014 10:38:14 +0100
From: Michal Simek <michal.simek@...inx.com>
To: Fengguang Wu <fengguang.wu@...el.com>
CC: Michal Simek <michal.simek@...inx.com>,
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.
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?
Thanks,
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists