From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <felipe.balbi@nokia.com>
Cc: "ext me@felipebalbi.com" <me@felipebalbi.com>,
"Gadiyar, Anand" <gadiyar@ti.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm: omap: ehci: avoid compiler error with touchbook
Date: Mon, 8 Mar 2010 15:04:23 -0800 [thread overview]
Message-ID: <20100308230422.GH2900@atomide.com> (raw)
In-Reply-To: <20100305070330.GB12757@nokia.com>
* Felipe Balbi <felipe.balbi@nokia.com> [100304 23:00]:
> On Thu, Mar 04, 2010 at 08:15:27PM +0100, ext me@felipebalbi.com wrote:
> >Hi,
> >
> >On Thu, 4 Mar 2010 18:33:15 +0530, "Gadiyar, Anand" <gadiyar@ti.com>
> >wrote:
> >>>This patch fixes that for the ehci_hdc_omap_platform_data.
> >>>
> >>
> >>should be ehci_hcd_omap_platform_data ;)
> >>
> >>BTW, this breaks compile for omap3-evm.
> >>Could you please build with omap3_defconfig and check.
> >
> >will do first thing tomorrow :-)
>
> yeah, it breaks because evm tries to assign to a (now) const
> variable. Maybe the only way is to move everybody out of the
> __initconst section and put them on __initdata.
>
> or we drop the revision check for EVM and use only the newer one,
> I'm more into doing the first one.
>
> Tony, do you have any comments ??
Hmm yeah thanks for digging into this mystery. Looks like we're
hitting some Linux initdata limitation.
We can't mark everything as __initconst. Some platform data can
get dynamically set based on the board type for resources.
So to me it sounds like the only solution is to mark everything
as __initdata and ignore the (correct) const for now for __initdata.
Or am I missing something?
Regards,
Tony
next prev parent reply other threads:[~2010-03-08 23:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 7:40 [PATCH 1/2] Revert "omap: Fix compile for early_param and omap_smc1" felipe.balbi
2010-03-04 7:40 ` [PATCH 2/2] arm: omap: ehci: avoid compiler error with touchbook felipe.balbi
2010-03-04 7:44 ` Felipe Balbi
2010-03-04 7:45 ` felipe.balbi
2010-03-04 13:03 ` Gadiyar, Anand
2010-03-04 19:15 ` me
2010-03-05 7:03 ` Felipe Balbi
2010-03-08 23:04 ` Tony Lindgren [this message]
2010-03-09 14:30 ` Felipe Balbi
2010-03-09 15:38 ` Tony Lindgren
2010-03-09 15:47 ` Felipe Balbi
2010-03-10 0:48 ` Tony Lindgren
2010-03-10 6:22 ` Felipe Balbi
2010-03-10 17:15 ` Tony Lindgren
2010-03-11 7:28 ` Felipe Balbi
2010-03-11 16:38 ` Tony Lindgren
2010-03-04 7:50 ` [PATCH 1/2] Revert "omap: Fix compile for early_param and omap_smc1" Felipe Balbi
2010-03-04 7:57 ` [PATCH 1/2] Manual revert of " felipe.balbi
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=20100308230422.GH2900@atomide.com \
--to=tony@atomide.com \
--cc=felipe.balbi@nokia.com \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=me@felipebalbi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox