From: Ben Dooks <ben-linux@fluff.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Grant Likely <grant.likely@secretlab.ca>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jean-Hugues Deschenes <jean-hugues.deschenes@octasic.com>
Subject: Re: linux-next: spi tree build failure
Date: Fri, 22 Jan 2010 04:27:08 +0000 [thread overview]
Message-ID: <20100122042708.GK10014@trinity.fluff.org> (raw)
In-Reply-To: <20100122152152.5666ccab.sfr@canb.auug.org.au>
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@canb.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.
next prev parent reply other threads:[~2010-01-22 4:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 4:21 linux-next: spi tree build failure Stephen Rothwell
2010-01-22 4:27 ` Ben Dooks [this message]
2010-01-22 17:31 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2010-01-21 3:57 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100122042708.GK10014@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=grant.likely@secretlab.ca \
--cc=jean-hugues.deschenes@octasic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.