All of lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: bcm: Don't build brcmstb SMP code when building for V6
Date: Fri, 22 Aug 2014 09:44:03 -0500	[thread overview]
Message-ID: <20140822144403.GU24407@sirena.org.uk> (raw)
In-Reply-To: <20140822050907.GC3246@norris-Latitude-E6410>

On Thu, Aug 21, 2014 at 10:09:07PM -0700, Brian Norris wrote:
> On Thu, Aug 21, 2014 at 09:06:34PM -0500, Mark Brown wrote:
> > From: Mark Brown <broonie@linaro.org>

> > building for -march=armv6 as happens when building allmodconfig. Since I
> > have not been able to identify a way to override the compiler architecture
> > selection per file add a Kconfig dependency to ensure this code is not
> > built if V6 support is enabled.

> I already proposed this solution to override the compiler architecture,
> in the same pattern as other similar code in the same directory.

>   http://article.gmane.org/gmane.linux.drivers.devicetree/84517

> My using 'CFLAGS_<obj> += <flags>', you can compile in v7.

I tried that but it wasn't doing the right thing for me - it appeared
since the compiler ends up getting both -march=armv7-a and -march=armv6
it complained that it couldn't satisfy both options.  It might be that
this is version dependant or the actual cause wsa something else, I
didn't investigate too hard.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140822/274418c1/attachment.sig>

  reply	other threads:[~2014-08-22 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22  2:06 [PATCH] ARM: bcm: Don't build brcmstb SMP code when building for V6 Mark Brown
2014-08-22  5:09 ` Brian Norris
2014-08-22 14:44   ` Mark Brown [this message]
2014-08-25 17:27     ` Brian Norris
2014-08-26 10:54       ` Arnd Bergmann

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=20140822144403.GU24407@sirena.org.uk \
    --to=broonie@kernel.org \
    --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 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.