From: Richard Weinberger <richard@nod.at>
To: linux-kernel@vger.kernel.org
Cc: linux-iio@vger.kernel.org, linux-pm@vger.kernel.org,
dwmw2@infradead.org, dbaryshkov@gmail.com, sre@kernel.org,
jassisinghbrar@gmail.com, pmeerw@pmeerw.net, lars@metafoo.de,
knaack.h@gmx.de, jic23@kernel.org, tglx@linutronix.de,
daniel.lezcano@linaro.org, Richard Weinberger <richard@nod.at>
Subject: [PATCH 1/6] clocksource/sh_cmt.c: Fix !HAS_IOMEM build
Date: Mon, 16 Mar 2015 22:27:05 +0100 [thread overview]
Message-ID: <1426541230-928-1-git-send-email-richard@nod.at> (raw)
Fixes:
drivers/clocksource/sh_cmt.c: In function ‘sh_cmt_map_memory’:
drivers/clocksource/sh_cmt.c:920:2: error: implicit declaration of function ‘ioremap_nocache’ [-Werror=implicit-function-declaration]
cmt->mapbase = ioremap_nocache(mem->start, resource_size(mem));
^
drivers/clocksource/sh_cmt.c:920:15: warning: assignment makes pointer from integer without a cast [enabled by default]
cmt->mapbase = ioremap_nocache(mem->start, resource_size(mem));
^
drivers/clocksource/sh_cmt.c: In function ‘sh_cmt_setup’:
drivers/clocksource/sh_cmt.c:1034:2: error: implicit declaration of function ‘iounmap’ [-Werror=implicit-function-declaration]
iounmap(cmt->mapbase);
Signed-off-by: Richard Weinberger <richard@nod.at>
---
drivers/clocksource/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
index 68161f7..c948f4e 100644
--- a/drivers/clocksource/Kconfig
+++ b/drivers/clocksource/Kconfig
@@ -192,6 +192,7 @@ config SYS_SUPPORTS_EM_STI
config SH_TIMER_CMT
bool "Renesas CMT timer driver" if COMPILE_TEST
depends on GENERIC_CLOCKEVENTS
+ depends on HAS_IOMEM
default SYS_SUPPORTS_SH_CMT
help
This enables build of a clocksource and clockevent driver for
--
1.8.4.5
next reply other threads:[~2015-03-16 21:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 21:27 Richard Weinberger [this message]
2015-03-16 21:27 ` [PATCH 2/6] clocksource/sh_mtu2.c: Fix !HAS_IOMEM build Richard Weinberger
[not found] ` <1426541230-928-2-git-send-email-richard-/L3Ra7n9ekc@public.gmane.org>
2015-03-17 8:19 ` Geert Uytterhoeven
2015-03-20 14:04 ` Daniel Lezcano
2015-03-16 21:27 ` [PATCH 3/6] clocksource/sh_tmu.c: " Richard Weinberger
2015-03-17 8:19 ` Geert Uytterhoeven
2015-03-20 14:05 ` Daniel Lezcano
2015-03-16 21:27 ` [PATCH 4/6] power/reset/rmobile-reset.c: " Richard Weinberger
2015-03-17 8:19 ` Geert Uytterhoeven
2015-03-20 12:31 ` Sebastian Reichel
2015-03-16 21:27 ` [PATCH 5/6] mailbox/altera.c: " Richard Weinberger
2015-03-16 21:27 ` [PATCH 6/6] iio/adc/cc10001_adc.c: " Richard Weinberger
[not found] ` <1426541230-928-6-git-send-email-richard-/L3Ra7n9ekc@public.gmane.org>
2015-03-21 11:35 ` Jonathan Cameron
[not found] ` <550D5772.2010400-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-03-30 19:40 ` Jonathan Cameron
[not found] ` <1426541230-928-1-git-send-email-richard-/L3Ra7n9ekc@public.gmane.org>
2015-03-17 8:18 ` [PATCH 1/6] clocksource/sh_cmt.c: " Geert Uytterhoeven
2015-03-20 14:05 ` Daniel Lezcano
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=1426541230-928-1-git-send-email-richard@nod.at \
--to=richard@nod.at \
--cc=daniel.lezcano@linaro.org \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jassisinghbrar@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=sre@kernel.org \
--cc=tglx@linutronix.de \
/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).