[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120619.214759.2265041580160751452.davem@davemloft.net>
Date: Tue, 19 Jun 2012 21:47:59 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: bhupesh.sharma@...com
Cc: sfr@...b.auug.org.au, netdev@...r.kernel.org,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
federico.vaga@...il.com, giancarlo.asnaghi@...com,
wg@...ndegger.com, mkl@...gutronix.de
Subject: Re: linux-next: build failure after merge of the net-next tree
From: Bhupesh SHARMA <bhupesh.sharma@...com>
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.
--
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