From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [CONSOLIDATED PULL 0/5] Fixes for M3
Date: Sun, 20 Jan 2013 20:40:36 -0800 [thread overview]
Message-ID: <cover.1358742751.git.sgw@linux.intel.com> (raw)
Richard,
This contains a better fix for the Oprofile/PPC issue from
Matthew along with the fix for non-GPLv3 issue from Chris L.
Thanks
Sau!
The following changes since commit 5892db9a34c188b8a9bdaa86e19ba62a7f4793b5:
oprofile: set correct kernel path (2013-01-20 13:13:54 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib sgw/stage
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/stage
Christopher Larson (1):
package.bbclass: drop unnecessary and broken packages.remove()
Cristian Iorga (1):
dbus: upgrade to 1.6.8
Darren Hart (1):
bb-matrix: Fix min and max calculations
Khem Raj (1):
boost: Upgrade 1.51 -> 1.52
Matthew McClintock (1):
oprofile: backport patches to fix ppc build issues
meta/classes/package.bbclass | 1 -
.../dbus/{dbus-1.6.4 => dbus-1.6.8}/dbus-1.init | 0
.../dbus/{dbus-1.6.4 => dbus-1.6.8}/ptest.patch | 0
.../dbus/{dbus-1.6.4 => dbus-1.6.8}/run-ptest | 0
.../{dbus-1.6.4 => dbus-1.6.8}/test-run-path.patch | 0
.../dbus/{dbus-1.6.4 => dbus-1.6.8}/tmpdir.patch | 0
.../{dbus-ptest_1.6.4.bb => dbus-ptest_1.6.8.bb} | 4 +-
meta/recipes-core/dbus/dbus_1.6.4.bb | 6 -
meta/recipes-core/dbus/dbus_1.6.8.bb | 6 +
...igure-to-look-for-libpfm4-function-first-.patch | 49 +++++++
...igure-to-handle-architectures-that-do-not.patch | 163 +++++++++++++++++++++
...y-perf_events-kernel-without-PERF_RECORD_.patch | 107 ++++++++++++++
...esn-t-build-for-32-bit-ppc-the-operf_util.patch | 32 ++++
meta/recipes-kernel/oprofile/oprofile_0.9.8.bb | 8 +-
meta/recipes-support/boost/boost.inc | 2 -
.../boost/{boost_1.51.0.bb => boost_1.52.0.bb} | 8 +-
meta/recipes-support/boost/files/hash_enums.patch | 45 ------
scripts/contrib/bb-perf/bb-matrix-plot.sh | 12 +-
scripts/contrib/bb-perf/bb-matrix.sh | 5 +-
19 files changed, 378 insertions(+), 70 deletions(-)
rename meta/recipes-core/dbus/{dbus-1.6.4 => dbus-1.6.8}/dbus-1.init (100%)
rename meta/recipes-core/dbus/{dbus-1.6.4 => dbus-1.6.8}/ptest.patch (100%)
rename meta/recipes-core/dbus/{dbus-1.6.4 => dbus-1.6.8}/run-ptest (100%)
rename meta/recipes-core/dbus/{dbus-1.6.4 => dbus-1.6.8}/test-run-path.patch (100%)
rename meta/recipes-core/dbus/{dbus-1.6.4 => dbus-1.6.8}/tmpdir.patch (100%)
rename meta/recipes-core/dbus/{dbus-ptest_1.6.4.bb => dbus-ptest_1.6.8.bb} (91%)
delete mode 100644 meta/recipes-core/dbus/dbus_1.6.4.bb
create mode 100644 meta/recipes-core/dbus/dbus_1.6.8.bb
create mode 100644 meta/recipes-kernel/oprofile/oprofile/0001-Change-configure-to-look-for-libpfm4-function-first-.patch
create mode 100644 meta/recipes-kernel/oprofile/oprofile/0001-Fix-up-configure-to-handle-architectures-that-do-not.patch
create mode 100644 meta/recipes-kernel/oprofile/oprofile/0001-Handle-early-perf_events-kernel-without-PERF_RECORD_.patch
create mode 100644 meta/recipes-kernel/oprofile/oprofile/0001-OProfile-doesn-t-build-for-32-bit-ppc-the-operf_util.patch
rename meta/recipes-support/boost/{boost_1.51.0.bb => boost_1.52.0.bb} (44%)
delete mode 100644 meta/recipes-support/boost/files/hash_enums.patch
--
1.8.0.2
reply other threads:[~2013-01-21 4:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cover.1358742751.git.sgw@linux.intel.com \
--to=sgw@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 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.