linux-next: build failure after merge of the spi tree
in [Kernel]
|
Prev: [PATCH 8/9] tracing/function-graph: Use correct string size for snprintf
Next: [ANNOUNCE] MDB Merkey's Kernel Debugger x86_64 2.6.34 06-28-2010
From: Stephen Rothwell on 28 Jun 2010 23:30 Hi Grant, After merging the spi tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/mmc/host/mmc_spi.c: In function 'mmc_spi_readbytes': drivers/mmc/host/mmc_spi.c:185: error: implicit declaration of function 'spi_sync_locked' drivers/mmc/host/mmc_spi.c: In function 'mmc_spi_request': drivers/mmc/host/mmc_spi.c:1088: error: implicit declaration of function 'spi_bus_lock' drivers/mmc/host/mmc_spi.c:1101: error: implicit declaration of function 'spi_bus_unlock' Caused by commit f0168ff4069fba07fdd4b05aa19f283171c8d265 ("spi/mmc_spi: mmc_spi adaptations for SPI bus locking API"). Maybe updates to another file were missed? I have used the spi tree from next-20100628 for today. -- Cheers, Stephen Rothwell sfr(a)canb.auug.org.au http://www.canb.auug.org.au/~sfr/
From: Grant Likely on 29 Jun 2010 01:10
On Mon, Jun 28, 2010 at 8:29 PM, Stephen Rothwell <sfr(a)canb.auug.org.au> wrote: > Hi Grant, > > After merging the spi tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/mmc/host/mmc_spi.c: In function 'mmc_spi_readbytes': > drivers/mmc/host/mmc_spi.c:185: error: implicit declaration of function 'spi_sync_locked' > drivers/mmc/host/mmc_spi.c: In function 'mmc_spi_request': > drivers/mmc/host/mmc_spi.c:1088: error: implicit declaration of function 'spi_bus_lock' > drivers/mmc/host/mmc_spi.c:1101: error: implicit declaration of function 'spi_bus_unlock' > > Caused by commit f0168ff4069fba07fdd4b05aa19f283171c8d265 ("spi/mmc_spi: > mmc_spi adaptations for SPI bus locking API"). �Maybe updates to another > file were missed? Yup, bad tree on my part. Reset back to 2.6.35-rc3 now. 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(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |