From: akuster808 <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core dizzy][PATCH 0/3] fixes for dizzy
Date: Thu, 29 Jan 2015 20:50:36 -0800 [thread overview]
Message-ID: <54CB0D9C.20801@gmail.com> (raw)
In-Reply-To: <1421294632-31110-1-git-send-email-ting.liu@freescale.com>
patches staged.
- armin
On 01/14/2015 08:03 PM, ting.liu@freescale.com wrote:
> From: Ting Liu <ting.liu@freescale.com>
>
> The following changes since commit e13f2681b75fd83aa3a1c823ad1c09faed0d6ae3
> rm_work: Fix RM_WORK_EXCLUDE for image/sdk recipes
>
> Ting Liu (3):
> libunwind: Fix test case link failure on PowerPC with Altivec
> bitbake.conf: add PKGDATA_DIR to BB_HASHBASE_WHITELIST
> valgrind: build with altivec only if it supported
>
> meta/conf/bitbake.conf | 2 +-
> .../pass-maltivec-only-if-it-supported.patch | 68 ++++++++++++++++++++++
> meta/recipes-devtools/valgrind/valgrind_3.9.0.bb | 1 +
> ...k-failure-on-PowerPC-systems-with-Altivec.patch | 28 +++++++++
> meta/recipes-support/libunwind/libunwind_1.1.bb | 4 ++
> 5 files changed, 102 insertions(+), 1 deletion(-)
> create mode 100644 meta/recipes-devtools/valgrind/valgrind/pass-maltivec-only-if-it-supported.patch
> create mode 100644 meta/recipes-support/libunwind/libunwind-1.1/Fix-test-case-link-failure-on-PowerPC-systems-with-Altivec.patch
>
prev parent reply other threads:[~2015-01-30 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 4:03 [oe-core dizzy][PATCH 0/3] fixes for dizzy ting.liu
2015-01-15 4:03 ` [oe-core dizzy][PATCH 1/3] libunwind: Fix test case link failure on PowerPC with Altivec ting.liu
2015-01-15 4:03 ` [oe-core dizzy][PATCH 2/3] bitbake.conf: add PKGDATA_DIR to BB_HASHBASE_WHITELIST ting.liu
2015-01-15 4:03 ` [oe-core dizzy][PATCH 3/3] valgrind: build with altivec only if it supported ting.liu
2015-01-30 4:50 ` akuster808 [this message]
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=54CB0D9C.20801@gmail.com \
--to=akuster808@gmail.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 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.