From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: linux-next: build failure after merge of the net-next tree Date: Tue, 19 Jun 2012 21:47:59 -0700 (PDT) Message-ID: <20120619.214759.2265041580160751452.davem@davemloft.net> References: <20120619.213703.513466167861199217.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from shards.monkeyblade.net ([149.20.54.216]:33730 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751568Ab2FTEsA (ORCPT ); Wed, 20 Jun 2012 00:48:00 -0400 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: bhupesh.sharma@st.com Cc: sfr@canb.auug.org.au, netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, federico.vaga@gmail.com, giancarlo.asnaghi@st.com, wg@grandegger.com, mkl@pengutronix.de From: Bhupesh SHARMA Date: Wed, 20 Jun 2012 12:45:46 +0800 > So, whether adding a check in Kconfig for HAVE_CLK be a proper > solution ? But that will limit the compilation of this driver for > only platforms which are ARM based. > > One may need to support this driver on x86 like platforms also.. Then x86 will need to provide clock operations, or there needs to be dummy ones for such platforms. This isn't rocket science.