linux-kernel - Re: linux-next: spi tree build failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 22 Jan 2010 10:31:43 -0700
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Ben Dooks <ben-linux@...ff.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jean-Hugues Deschenes <jean-hugues.deschenes@...asic.com>
Subject: Re: linux-next: spi tree build failure

On Thu, Jan 21, 2010 at 9:27 PM, Ben Dooks <ben-linux@...ff.org> wrote:
> On Fri, Jan 22, 2010 at 03:21:52PM +1100, Stephen Rothwell wrote:
>> Hi Grant,
>>
>> Today's linux-next build (x86_64 allmodconfig) failed like this:
>>
>> ERROR: "clk_get_rate" [drivers/spi/dw_spi_mmio.ko] undefined!
>> ERROR: "clk_enable" [drivers/spi/dw_spi_mmio.ko] undefined!
>> ERROR: "clk_get" [drivers/spi/dw_spi_mmio.ko] undefined!
>> ERROR: "clk_put" [drivers/spi/dw_spi_mmio.ko] undefined!
>> ERROR: "clk_disable" [drivers/spi/dw_spi_mmio.ko] undefined!
>>
>> Caused by commit f7b6fd6d1d3833529f1626c761ba7e338586d35e ("Memory-mapped
>> dw_spi driver").
>
> sounds like someone forgot to tmake the driver dependant on HAVE_CLK

Gah!  I did a test build of the module with allmodconfig, but I didn't
let it get to the modpost stage ('cause I'm building on my dinky
laptop which takes forever).  Sorry.  I've picked up the fix and
pushed out.  Today's tree should be better.  I'm not picking up
anything new today.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
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/