Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Phil Blundell <pb@pbcl.net>, Andre McCurdy <armccurdy@gmail.com>,
	Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-configure-common.inc: duplicate armv7a over-ride for armv8a
Date: Thu, 24 Mar 2016 21:41:17 +0000	[thread overview]
Message-ID: <1458855677.3073.35.camel@linuxfoundation.org> (raw)
In-Reply-To: <1458844322.3476.198.camel@pbcl.net>

On Thu, 2016-03-24 at 18:32 +0000, Phil Blundell wrote:
> On Thu, 2016-03-24 at 10:37 -0700, Andre McCurdy wrote:
> > 
> > Renaming armv8a -> aarch32 is going to affect almost every line in
> > the patch. We should probably drop the current patch from master-
> > next.
> 
> "AArch32" applies retrospectively to all older versions of the ARM
> architecture as well, so it's not obvious to me that a straight
> rename
> of the existing "armv8a" override to "aarch32" would be the right
> thing
> either. 
> 
> I think the whole approach to ARMv8 and AArch64 in OE needs to be
> carefully thought through before we start landing any patches for
> that
> stuff.  We have a tangled enough maze of overrides right now and I
> think we should make all efforts to avoid it getting worse.

Agreed, I'm planning to drop the patch triggering this from -next and
defer it until 2.2. The discussions can happen in the meantime to get a
patchset we're all happy with.

Cheers,

Richard


  reply	other threads:[~2016-03-24 21:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24  3:19 [PATCH] gcc-configure-common.inc: duplicate armv7a over-ride for armv8a Andre McCurdy
2016-03-24  4:19 ` Khem Raj
2016-03-24  5:16   ` Andre McCurdy
2016-03-24  8:03     ` Khem Raj
2016-03-24 17:37       ` Andre McCurdy
2016-03-24 18:32         ` Phil Blundell
2016-03-24 21:41           ` Richard Purdie [this message]
2016-03-24 22:28             ` Khem Raj
2016-03-24 22:22           ` Khem Raj
2016-03-24 23:21             ` Phil Blundell
2016-03-24 23:58               ` Khem Raj

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=1458855677.3073.35.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pb@pbcl.net \
    --cc=raj.khem@gmail.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