From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753769AbaCKEqW (ORCPT <rfc822;w@1wt.eu>);
	Tue, 11 Mar 2014 00:46:22 -0400
Received: from [143.182.124.37] ([143.182.124.37]:11959 "EHLO mga14.intel.com"
	rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP
	id S1751985AbaCKEqU (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 11 Mar 2014 00:46:20 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.97,629,1389772800"; 
   d="scan'208";a="489537752"
Date: Tue, 11 Mar 2014 12:45:55 +0800
From: Fengguang Wu <fengguang.wu@intel.com>
To: Michal Simek <michal.simek@xilinx.com>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org,
        Marc Kleine-Budde <mkl@pengutronix.de>, monstr@monstr.eu,
        devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
        netdev@vger.kernel.org, linux-can@vger.kernel.org, robh+dt@kernel.org,
        Kedareswara rao Appana <appana.durga.rao@xilinx.com>,
        grant.likely@linaro.org, Kedareswara rao Appana <appanad@xilinx.com>,
        wg@grandegger.com
Subject: Re: [PATCH v5] can: xilinx CAN controller support.
Message-ID: <20140311044555.GA12373@localhost>
References: <5254bfec-c6fd-4681-a34d-706d51e60fbb@VA3EHSMHS004.ehs.local>
 <531DD493.3030306@monstr.eu>
 <531DD5E7.7090406@pengutronix.de>
 <3245971.RIuVmbVL0Z@wuerfel>
 <1964213d-6bd9-49fa-805e-42e1e0630fd5@VA3EHSMHS029.ehs.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1964213d-6bd9-49fa-805e-42e1e0630fd5@VA3EHSMHS029.ehs.local>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

> > 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.

Thanks,
Fengguang