From: fengguang.wu@intel.com (Fengguang Wu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] can: xilinx CAN controller support.
Date: Thu, 13 Mar 2014 19:21:12 +0800 [thread overview]
Message-ID: <20140313112112.GB8806@localhost> (raw)
In-Reply-To: <546dbc60-dd7b-4249-bab8-ad7e008b9aad@AM1EHSMHS001.ehs.local>
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
next prev parent reply other threads:[~2014-03-13 11:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 13:20 [PATCH v5] can: xilinx CAN controller support Kedareswara rao Appana
2014-03-04 23:51 ` Sören Brinkmann
2014-03-05 6:58 ` Oliver Hartkopp
2014-03-05 7:04 ` Appana Durga Kedareswara Rao
[not found] ` <20140304235115.GN13293@xsjandreislx>
2014-03-05 7:03 ` Appana Durga Kedareswara Rao
2014-03-10 14:57 ` Marc Kleine-Budde
2014-03-10 15:04 ` Michal Simek
2014-03-10 15:10 ` Marc Kleine-Budde
2014-03-10 15:15 ` Arnd Bergmann
2014-03-10 15:26 ` Michal Simek
2014-03-11 4:45 ` Fengguang Wu
2014-03-11 9:38 ` Michal Simek
2014-03-13 11:21 ` Fengguang Wu [this message]
2014-03-11 12:34 ` Appana Durga Kedareswara Rao
2014-03-11 12:48 ` Marc Kleine-Budde
2014-03-11 14:08 ` Appana Durga Kedareswara Rao
2014-03-11 14:31 ` Marc Kleine-Budde
2014-03-12 10:18 ` Michal Simek
2014-03-12 16:18 ` Sören Brinkmann
2014-03-12 10:01 ` Michal Simek
2014-03-20 4:41 ` Appana Durga Kedareswara Rao
2014-03-10 15:15 ` Rob Herring
2014-03-10 15:22 ` Michal Simek
[not found] ` <531DD8C3.5050006@xilinx.com>
2014-03-11 12:35 ` Appana Durga Kedareswara Rao
[not found] <1393939253-30245-1-git-send-email-appanad@xilinx.com>
2014-03-10 7:12 ` Appana Durga Kedareswara Rao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140313112112.GB8806@localhost \
--to=fengguang.wu@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).