public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Samuel Ortiz <sameo@linux•intel.com>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: [PATCH -next] mfd: ab8500 depends on SPI_MASTER
Date: Tue, 14 Sep 2010 15:23:51 -0700	[thread overview]
Message-ID: <20100914152351.0ba53b5d.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100914135802.c99d3672.sfr@canb.auug.org.au>

From: Randy Dunlap <randy.dunlap@oracle•com>

Fix build errors in ab8500-spi.c.  It uses spi_* functions, so it
should depend on SPI_MASTER.

ab8500-spi.c:(.text+0x4900a): undefined reference to `spi_sync'
ab8500-spi.c:(.text+0x490b0): undefined reference to `spi_sync'
ab8500-spi.c:(.init.text+0x30c5): undefined reference to `spi_register_driver'

Signed-off-by: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Samuel Ortiz <sameo@linux•intel.com>
---
 drivers/mfd/Kconfig |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-next-20100914.orig/drivers/mfd/Kconfig
+++ linux-next-20100914/drivers/mfd/Kconfig
@@ -475,7 +475,7 @@ config EZX_PCAP
 
 config AB8500_CORE
 	bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
-	depends on GENERIC_HARDIRQS && ABX500_CORE
+	depends on GENERIC_HARDIRQS && ABX500_CORE && SPI_MASTER
 	select MFD_CORE
 	help
 	  Select this option to enable access to AB8500 power management

  reply	other threads:[~2010-09-14 22:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14  3:58 linux-next: Tree for September 14 Stephen Rothwell
2010-09-14 22:23 ` Randy Dunlap [this message]
2010-09-14 22:23 ` [PATCH -next] staging: cx25821 and go7007 depend on IR_CORE Randy Dunlap
2010-09-16 19:33   ` Greg KH

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=20100914152351.0ba53b5d.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sameo@linux$(echo .)intel.com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox