From: Tony Lindgren <tony@atomide.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-omap@vger.kernel.org, Charulatha Varadarajan <charu@ti.com>,
Rajendra Nayak <rnayak@ti.com>,
"Govindraj R." <govindraj.raja@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [GIT PULL] for testing: OMAP hwmod driver conversions: watchdog, UART, i2c
Date: Wed, 29 Sep 2010 19:29:37 -0700 [thread overview]
Message-ID: <20100930022937.GF3117@atomide.com> (raw)
In-Reply-To: <20100930021819.GD3117@atomide.com>
* Tony Lindgren <tony@atomide.com> [100929 19:10]:
>
> Then trying to build for omap1 OSK fails with:
>
> In file included from arch/arm/plat-omap/common.c:35:
> arch/arm/plat-omap/include/plat/control.h:20:40: error: mach/ctrl_module_core_44xx.h: No such file or directory
> arch/arm/plat-omap/include/plat/control.h:21:40: error: mach/ctrl_module_wkup_44xx.h: No such file or directory
> arch/arm/plat-omap/include/plat/control.h:22:44: error: mach/ctrl_module_pad_core_44xx.h: No such file or directory
> arch/arm/plat-omap/include/plat/control.h:23:44: error: mach/ctrl_module_pad_wkup_44xx.h: No such file or directory
This seems to be related to Santosh' commit 802edcb7.
Santosh, can you do a patch to fix this against the current
omap-for-linus branch?
Regards,
Tony
next prev parent reply other threads:[~2010-09-30 2:29 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 18:24 [GIT PULL] for testing: OMAP hwmod driver conversions: watchdog, UART, i2c Kevin Hilman
2010-09-28 20:18 ` Tony Lindgren
2010-09-28 21:35 ` Kevin Hilman
2010-09-29 4:01 ` Nayak, Rajendra
2010-09-29 16:14 ` Nayak, Rajendra
2010-09-29 16:17 ` Nayak, Rajendra
2010-09-29 19:18 ` Kevin Hilman
2010-09-29 19:28 ` Nayak, Rajendra
2010-09-29 19:40 ` Kevin Hilman
2010-09-29 19:54 ` Nayak, Rajendra
2010-09-29 20:03 ` Kevin Hilman
2010-09-29 19:16 ` Kevin Hilman
2010-09-29 22:24 ` Kevin Hilman
2010-09-30 2:18 ` Tony Lindgren
2010-09-30 2:29 ` Tony Lindgren [this message]
2010-09-30 7:55 ` Shilimkar, Santosh
2010-10-01 23:38 ` Paul Walmsley
2010-10-01 23:48 ` Paul Walmsley
2010-09-30 14:39 ` Kevin Hilman
2010-09-30 15:13 ` Kevin Hilman
[not found] ` <877hi3gqq7.fsf@deeprootsystems.com>
2010-10-01 13:28 ` Nayak, Rajendra
2010-10-01 15:07 ` Kevin Hilman
2010-10-01 20:47 ` Kevin Hilman
2010-10-02 0:47 ` Tony Lindgren
2010-10-01 16:42 ` Cousson, Benoit
2010-10-05 6:01 ` Paul Walmsley
2010-10-05 6:20 ` Nayak, Rajendra
2010-10-05 6:24 ` Paul Walmsley
2010-10-05 6:27 ` Paul Walmsley
2010-10-05 12:33 ` Nayak, Rajendra
2010-10-05 13:13 ` Nayak, Rajendra
2010-10-05 16:58 ` Paul Walmsley
2010-10-05 18:09 ` Paul Walmsley
2010-10-05 18:48 ` Nayak, Rajendra
2010-10-05 17:04 ` Kevin Hilman
2010-10-05 18:53 ` Nayak, Rajendra
2010-10-05 19:49 ` Kevin Hilman
2010-10-05 20:26 ` Nayak, Rajendra
2010-10-05 20:35 ` Kevin Hilman
2010-10-05 20:41 ` Nayak, Rajendra
2010-10-05 20:44 ` Kevin Hilman
2010-10-05 20:46 ` Nayak, Rajendra
2010-10-05 15:46 ` Cousson, Benoit
2010-09-30 15:46 ` Tony Lindgren
2010-09-29 14:51 ` Varadarajan, Charulatha
2010-09-29 15:20 ` Kevin Hilman
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=20100930022937.GF3117@atomide.com \
--to=tony@atomide.com \
--cc=charu@ti.com \
--cc=govindraj.raja@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.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.