From: "Vincent Stehlé" <v-stehle@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: "Vincent Stehlé" <vincent.stehle@laposte.net>,
"Tony Lindgren" <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP5: select SCU
Date: Thu, 16 May 2013 16:29:07 +0200 [thread overview]
Message-ID: <5194ED33.7050502@ti.com> (raw)
In-Reply-To: <5194DAC5.9080203@ti.com>
So the exact commit breaking OMAP5 link for me is:
883a106 ARM: default machine descriptor for multiplatform
The breakage seems to be a side effect of not selecting ARCH_VEXPRESS
any more, which causes HAVE_ARM_SCU to not be selected any more, too,
when compiling only for OMAP5. IMHO this only reveals a deeper issue.
Probably the ideal fix would be to remove all references to the scu_
functions for OMAP5, but those seem to exist in files and functions,
common to OMAP4 and 5 (sleep44xx.S, omap-smp.c).
How would you deal with that, please?
Best regards,
V.
next prev parent reply other threads:[~2013-05-16 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 16:57 [PATCH] ARM: OMAP5: select SCU Vincent Stehlé
2013-05-15 12:36 ` Santosh Shilimkar
2013-05-16 13:10 ` Vincent Stehlé
2013-05-16 14:29 ` Vincent Stehlé [this message]
2013-05-17 7:16 ` Shilimkar, Santosh
2013-05-16 16:00 ` [RFC PATCH v2] ARM: OMAP4+: protect SCU code compilation Vincent Stehlé
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=5194ED33.7050502@ti.com \
--to=v-stehle@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
--cc=vincent.stehle@laposte.net \
/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