[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090625032407.GO6027@tarshish>
Date: Thu, 25 Jun 2009 06:24:08 +0300
From: Baruch Siach <baruch@...s.co.il>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Linus <torvalds@...ux-foundation.org>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Ben Dooks <ben-linux@...ff.org>
Subject: Re: linux-next: origin tree build failure
Hi Stephen,
On Thu, Jun 25, 2009 at 11:13:44AM +1000, Stephen Rothwell wrote:
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> ERROR: "clk_enable" [drivers/i2c/busses/i2c-designware.ko] undefined!
> ERROR: "clk_disable" [drivers/i2c/busses/i2c-designware.ko] undefined!
> ERROR: "clk_put" [drivers/i2c/busses/i2c-designware.ko] undefined!
> ERROR: "clk_get_rate" [drivers/i2c/busses/i2c-designware.ko] undefined!
> ERROR: "clk_get" [drivers/i2c/busses/i2c-designware.ko] undefined!
>
> Caused by commit 1ab52cf910bbbee92861227e6ed77c56b1dc233c ("i2c: driver
> for the Synopsys DesignWare I2C controller") from Linus' tree which I
> have reverted for today.
So, what is the right configuration symbol to depend on for the clk API?
A short archives search led to the "provide a dummy implementation of the clk
API" patch from Uwe Kleine-KÃnig
(http://lkml.indiana.edu/hypermail/linux/kernel/0804.2/2748.html). Is this the
right solution?
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@...s.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
--
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