From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
linux-omap@vger.kernel.org, Olof Johansson <olof@lixom.net>
Subject: Re: OMAP totally fucked?
Date: Sat, 3 Mar 2012 18:29:06 +0000 [thread overview]
Message-ID: <201203031829.06992.arnd@arndb.de> (raw)
In-Reply-To: <20120303180428.GA10293@atomide.com>
On Saturday 03 March 2012, Tony Lindgren wrote:
> Well 85631d2 builds fine, looks like now some more includes of
> plat/hardware.h are now needed.Have not yet tracked down which
> commit triggers the build errors. Eventually those should become
> local headers too..
I've tried building arm-soc/for-next and rmk/for-next, they are both
fine, just merging the two gives me the same build errors that Russell
saw.
Adding plat/hardware.h in all files that break solves the problems,
aside from the iommu dependency for rpmsg for which Ohad has provided
a fix already that I should pull.
Arnd
next prev parent reply other threads:[~2012-03-03 18:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 15:46 OMAP totally fucked? Russell King - ARM Linux
2012-03-03 18:04 ` Tony Lindgren
2012-03-03 18:29 ` Arnd Bergmann [this message]
2012-03-03 21:05 ` Tony Lindgren
2012-03-04 15:59 ` Russell King - ARM Linux
2012-03-05 19:07 ` Tony Lindgren
2012-03-06 19:45 ` Kevin Hilman
2012-03-06 19:55 ` Tony Lindgren
2012-03-06 20:15 ` Kevin Hilman
2012-03-06 21:23 ` Tony Lindgren
2012-03-03 18:32 ` Russell King - ARM Linux
2012-03-03 19:01 ` Tony Lindgren
2012-03-03 19:28 ` Russell King - ARM Linux
2012-03-03 20:01 ` Tony Lindgren
2012-03-03 20:28 ` Tony Lindgren
2012-03-03 20:34 ` Tony Lindgren
2012-03-03 20:52 ` Russell King - ARM Linux
2012-03-03 21:21 ` Tony Lindgren
2012-03-03 21:57 ` Tony Lindgren
2012-03-06 14:58 ` Cousson, Benoit
2012-03-06 15:08 ` Russell King - ARM Linux
2012-03-06 15:41 ` Arnd Bergmann
2012-03-06 15:29 ` Peter Ujfalusi
2012-03-06 20:14 ` Tony Lindgren
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=201203031829.06992.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.