From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: 3.8 no mach include directory anymore?
Date: Fri, 5 Apr 2013 11:22:06 +0200 [thread overview]
Message-ID: <20130405092206.GA10373@pengutronix.de> (raw)
In-Reply-To: <15525047.PsIxlFA1vB@dabox>
Hi Tim,
On Fri, Apr 05, 2013 at 08:13:02AM +0200, Tim Sander wrote:
> Hi
>
> I have a small driver which uses the MX35_IO_ADDRESS which had been defined in
> #include <mach/mx35.h>
A driver should never use MX35_IO_ADDRESS.
> but while the mx35.h file still exist the include directory has vanished?
>
> Any idea how to get the module compiling again with 3.8?
Use ioremap, add whatever hack is necessary, or very much preferred:
Convert you board over to devicetree and retrieve the base address
properly from there.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2013-04-05 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 6:13 3.8 no mach include directory anymore? Tim Sander
2013-04-05 9:22 ` Sascha Hauer [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=20130405092206.GA10373@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).