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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100122042708.GK10014@trinity.fluff.org>
Date:	Fri, 22 Jan 2010 04:27:08 +0000
From:	Ben Dooks <ben-linux@...ff.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Grant Likely <grant.likely@...retlab.ca>,
	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 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
 
> I have used the spi tree from next-20100120 again for today.
> -- 
> Cheers,
> Stephen Rothwell                    sfr@...b.auug.org.au
> http://www.canb.auug.org.au/~sfr/



-- 
-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

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