From: Cristian Iorga <cristian.iorga@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Various comms and multimedia PUs
Date: Wed, 27 Aug 2014 21:10:00 +0300 [thread overview]
Message-ID: <cover.1409162830.git.cristian.iorga@intel.com> (raw)
Various PUs for comms and multimedia
The below warnings are due to the original test source code present
in ofono test suite!
WARNING: Trailing white space detected at these locations
pull-25158/0004-ofono-upgrade-to-1.15.patch:138:+
pull-25158/0004-ofono-upgrade-to-1.15.patch:148:+
pull-25158/0004-ofono-upgrade-to-1.15.patch:150:+
.....
The following changes since commit c16795477ea7e2159b5d3808268912b572887e2d:
qemu: add PACKAGECONFIG for numa (2014-08-27 12:13:38 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ciorga/PUs
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ciorga/PUs
Cristian Iorga (4):
connman: upgrade to 1.25
harfbuzz: upgrade to 0.9.35
bluez5: upgrade to 5.22
ofono: upgrade to 1.15
meta/recipes-connectivity/bluez5/bluez5_5.21.bb | 3 -
meta/recipes-connectivity/bluez5/bluez5_5.22.bb | 3 +
...ild-libppp-plugin-without-versioning-info.patch | 32 -
.../connman/{connman_1.24.bb => connman_1.25.bb} | 5 +-
.../ofono/Revert-test-Convert-to-Python-3.patch | 1270 ++++++++++++++++++++
.../ofono/{ofono_1.14.bb => ofono_1.15.bb} | 7 +-
.../{harfbuzz_0.9.29.bb => harfbuzz_0.9.35.bb} | 4 +-
7 files changed, 1280 insertions(+), 44 deletions(-)
delete mode 100644 meta/recipes-connectivity/bluez5/bluez5_5.21.bb
create mode 100644 meta/recipes-connectivity/bluez5/bluez5_5.22.bb
delete mode 100644 meta/recipes-connectivity/connman/connman/build-libppp-plugin-without-versioning-info.patch
rename meta/recipes-connectivity/connman/{connman_1.24.bb => connman_1.25.bb} (59%)
create mode 100644 meta/recipes-connectivity/ofono/ofono/Revert-test-Convert-to-Python-3.patch
rename meta/recipes-connectivity/ofono/{ofono_1.14.bb => ofono_1.15.bb} (45%)
rename meta/recipes-graphics/harfbuzz/{harfbuzz_0.9.29.bb => harfbuzz_0.9.35.bb} (88%)
--
1.9.1
next reply other threads:[~2014-08-27 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 18:10 Cristian Iorga [this message]
2014-08-27 18:10 ` [PATCH 1/4] connman: upgrade to 1.25 Cristian Iorga
2014-08-27 18:10 ` [PATCH 2/4] harfbuzz: upgrade to 0.9.35 Cristian Iorga
2014-08-27 18:10 ` [PATCH 3/4] bluez5: upgrade to 5.22 Cristian Iorga
2014-08-27 18:10 ` [PATCH 4/4] ofono: upgrade to 1.15 Cristian Iorga
-- strict thread matches above, loose matches on Subject: below --
2014-02-27 16:07 [PATCH 0/4] Various Comms and Multimedia PUs Cristian Iorga
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.1409162830.git.cristian.iorga@intel.com \
--to=cristian.iorga@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