From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ralf Baechle <ralf@linux-mips.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rtc: rtc-ds1286 and rtc-m48t35 need <linux/io.h>
Date: Thu, 16 Oct 2008 14:18:02 +0200 [thread overview]
Message-ID: <20081016121802.GA7248@alpha.franken.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0810160927340.25608@anakin>
On Thu, Oct 16, 2008 at 09:28:47AM +0200, Geert Uytterhoeven wrote:
> With m68k allmodconfig, I get:
>
> | drivers/rtc/rtc-ds1286.c: In function 'ds1286_rtc_read':
> | drivers/rtc/rtc-ds1286.c:33: error: implicit declaration of function '__raw_readl'
> | drivers/rtc/rtc-ds1286.c: In function 'ds1286_rtc_write':
> | drivers/rtc/rtc-ds1286.c:38: error: implicit declaration of function '__raw_writel'
> | drivers/rtc/rtc-ds1286.c: In function 'ds1286_probe':
> | drivers/rtc/rtc-ds1286.c:345: error: implicit declaration of function 'ioremap'
> | drivers/rtc/rtc-ds1286.c:345: warning: assignment makes pointer from integer without a cast
> | drivers/rtc/rtc-ds1286.c:365: error: implicit declaration of function 'iounmap'
>
> and
>
> | drivers/rtc/rtc-m48t35.c: In function 'm48t35_read_time':
> | drivers/rtc/rtc-m48t35.c:59: error: implicit declaration of function 'readb'
> | drivers/rtc/rtc-m48t35.c:60: error: implicit declaration of function 'writeb'
> | drivers/rtc/rtc-m48t35.c: In function 'm48t35_probe':
> | drivers/rtc/rtc-m48t35.c:168: error: implicit declaration of function 'ioremap'
> | drivers/rtc/rtc-m48t35.c:168: warning: assignment makes pointer from integer without a cast
> | drivers/rtc/rtc-m48t35.c:188: error: implicit declaration of function 'iounmap'
>
> Include <linux/io.h> to get access to the I/O API.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Thanks for fixing and sorry for that. I'll do more build tests in
the future to avoid that.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2008-10-16 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 7:28 [PATCH] rtc: rtc-ds1286 and rtc-m48t35 need <linux/io.h> Geert Uytterhoeven
2008-10-16 12:18 ` Thomas Bogendoerfer [this message]
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=20081016121802.GA7248@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=torvalds@linux-foundation.org \
/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