From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] valgrind: don't restrict to armv7a
Date: Fri, 8 Jan 2016 14:43:18 +0200 [thread overview]
Message-ID: <568FAEE6.2090502@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZi8hpETfuWBOTan=8B83V5up_fzM2__rK4ZmXZXf2UPg@mail.gmail.com>
On 01/07/2016 11:39 PM, Burton, Ross wrote:
>
> On 7 January 2016 at 21:03, Andre McCurdy <armccurdy@gmail.com
> <mailto:armccurdy@gmail.com>> wrote:
>
> Ping. This is more urgent now that arch-armv7ve.inc has been merged to
> oe-core master.
>
>
> Sadly 3.11 totally breaks on PPC, so that's blocking. Maybe rebase the
> patch to master before the 3.11 upgrade?
I'll fix the PPC breakage and resend (with Andre's fix commits if they
aren't yet in master against old version by then).
Alex
next prev parent reply other threads:[~2016-01-08 12:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 23:57 [PATCH 0/3] valgrind fixes Andre McCurdy
2015-12-22 23:57 ` [PATCH 1/3] security_flags.inc: disable -fstack-protector-XXX for valgrind Andre McCurdy
2015-12-22 23:57 ` [PATCH 2/3] valgrind: don't restrict to armv7a Andre McCurdy
2016-01-07 21:03 ` Andre McCurdy
2016-01-07 21:39 ` Burton, Ross
2016-01-08 12:43 ` Alexander Kanavin [this message]
2015-12-22 23:58 ` [PATCH 3/3] valgrind: include aarch64 in COMPATIBLE_HOST Andre McCurdy
-- strict thread matches above, loose matches on Subject: below --
2016-01-08 14:57 [PATCH 0/3] Valgrind: update to 3.11.0 Alexander Kanavin
2016-01-08 14:57 ` [PATCH 2/3] valgrind: don't restrict to armv7a Alexander Kanavin
2016-01-13 2:13 ` dengke.du
2016-01-13 2:18 ` dengke.du
2016-01-13 3:23 ` Andre McCurdy
2016-01-13 5:00 ` 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=568FAEE6.2090502@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox