From: Mark Hatle <mark.hatle@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Matt Madison <matt@madison.systems>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] ARMPKGSFX_FP ordering
Date: Mon, 7 Dec 2015 09:17:33 -0600 [thread overview]
Message-ID: <5665A30D.7010306@windriver.com> (raw)
In-Reply-To: <CAJTo0LYNtGDhyZLJnRum7XveZJ4eG1m6wvgTe8H3Sb9fpburUg@mail.gmail.com>
On 12/7/15 8:01 AM, Burton, Ross wrote:
>
> On 6 December 2015 at 18:22, Matt Madison <matt@madison.systems
> <mailto:matt@madison.systems>> wrote:
>
> Close, but not quite, I think. It doesn't look like it addresses the
> ordering mismatch that occurs due to the -vfp include being processed
> before the -neon include, resulting vfpv4 preceding neon in
> ARMPKGSFX_FPU when both are enabled.
>
>
> Martin's patch is in my ross/mut branch so will be in master soon, can you
> rebase these patches please?
>
> Ross
>
>
I would prefer we fix the package extra arch, and leave the ARMPKGSFX_FPU alone.
I believe that order is correct.
--Mark
next prev parent reply other threads:[~2015-12-07 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 17:09 [PATCH 0/1] ARMPKGSFX_FP ordering Matt Madison
2015-12-06 17:09 ` [PATCH 1/1] feature-arm-neon.inc, feature-arm-vfp.inc: fix vfpv4 suffix ordering Matt Madison
2015-12-06 17:47 ` [PATCH 0/1] ARMPKGSFX_FP ordering Martin Jansa
2015-12-06 18:22 ` Matt Madison
2015-12-07 14:01 ` Burton, Ross
2015-12-07 15:17 ` Mark Hatle [this message]
2015-12-07 15:49 ` Matt Madison
2015-12-12 17:02 ` Matt Madison
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=5665A30D.7010306@windriver.com \
--to=mark.hatle@windriver.com \
--cc=matt@madison.systems \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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.