netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: kishon@ti.com, anton@enomsg.org, dwmw2@infradead.org,
	richardcochran@gmail.com, lidza.louina@gmail.com,
	gregkh@linuxfoundation.org, jic23@kernel.org,
	davem@davemloft.net
Cc: sebastian.hesselbarth@gmail.com, florian@openwrt.org,
	thomas.petazzoni@free-electrons.com, lars@metafoo.de,
	marex@denx.de, acourbot@nvidia.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	driverdev-devel@linuxdriverproject.org,
	devel@driverdev.osuosl.org, linux-iio@vger.kernel.org,
	Richard Weinberger <richard@nod.at>
Subject: [PATCH 3/7] staging,spear_adc: Add dependency on HAS_IOMEM
Date: Tue, 14 Jan 2014 16:45:41 +0100	[thread overview]
Message-ID: <1389714345-20165-3-git-send-email-richard@nod.at> (raw)
In-Reply-To: <1389714345-20165-1-git-send-email-richard@nod.at>

On archs like S390 or um this driver cannot build nor work.
Make it depend on HAS_IOMEM to bypass build failures.

drivers/staging/iio/adc/spear_adc.c: In function ‘spear_adc_probe’:
drivers/staging/iio/adc/spear_adc.c:393:2: error: implicit declaration of function ‘iounmap’ [-Werror=implicit-function-declaration

Signed-off-by: Richard Weinberger <richard@nod.at>
---
 drivers/staging/iio/adc/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/staging/iio/adc/Kconfig b/drivers/staging/iio/adc/Kconfig
index e3d6430..7d5d675 100644
--- a/drivers/staging/iio/adc/Kconfig
+++ b/drivers/staging/iio/adc/Kconfig
@@ -128,6 +128,7 @@ config MXS_LRADC
 config SPEAR_ADC
 	tristate "ST SPEAr ADC"
 	depends on PLAT_SPEAR || COMPILE_TEST
+	depends on HAS_IOMEM
 	help
 	  Say yes here to build support for the integrated ADC inside the
 	  ST SPEAr SoC. Provides direct access via sysfs.
-- 
1.8.1.4

  parent reply	other threads:[~2014-01-14 15:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 15:45 [PATCH 1/7] ptp_pch: Add dependency on HAS_IOMEM Richard Weinberger
2014-01-14 15:45 ` [PATCH 2/7] staging,dgap: " Richard Weinberger
2014-01-14 15:45 ` Richard Weinberger [this message]
     [not found]   ` <1389714345-20165-3-git-send-email-richard-/L3Ra7n9ekc@public.gmane.org>
2014-01-18 11:41     ` [PATCH 3/7] staging,spear_adc: " Jonathan Cameron
2014-01-14 15:45 ` [PATCH 4/7] phy,exynos: " Richard Weinberger
2014-01-14 15:45 ` [PATCH 5/7] net,marvell: " Richard Weinberger
2014-01-14 15:45 ` [PATCH 6/7] power,goldfish: " Richard Weinberger
2014-01-14 15:45 ` [PATCH 7/7] staging,lpc32xx_adc: " Richard Weinberger
2014-01-18 11:50   ` Jonathan Cameron
2014-01-15 22:51 ` [PATCH 1/7] ptp_pch: " David Miller

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=1389714345-20165-3-git-send-email-richard@nod.at \
    --to=richard@nod.at \
    --cc=acourbot@nvidia.com \
    --cc=anton@enomsg.org \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=dwmw2@infradead.org \
    --cc=florian@openwrt.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=kishon@ti.com \
    --cc=lars@metafoo.de \
    --cc=lidza.louina@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=thomas.petazzoni@free-electrons.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).