From: Cristian Iorga <cristian.iorga@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Various Comms and Multimedia PUs
Date: Thu, 27 Feb 2014 18:07:29 +0200 [thread overview]
Message-ID: <cover.1393517205.git.cristian.iorga@intel.com> (raw)
The following changes since commit 5ab9d7e28f987fba8bab03bb7851c263f746c208:
security-flags: Avoid lttng-tools issue on arm (2014-02-26 13:48:21 +0000)
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):
wpa-supplicant: upgrade to 2.1
bluez5: upgrade to 5.15
telepathy-glib: upgrade to 0.23.2
telepathy-mission-control: upgrade to 5.16.1
meta/recipes-connectivity/bluez5/bluez5_5.14.bb | 5 -
meta/recipes-connectivity/bluez5/bluez5_5.15.bb | 4 +
...thy-glib_0.23.0.bb => telepathy-glib_0.23.2.bb} | 7 +-
...16.0.bb => telepathy-mission-control_5.16.1.bb} | 10 +-
.../{wpa-supplicant-2.0.inc => wpa-supplicant.inc} | 8 +-
.../wpa-supplicant/wpa-supplicant/defconfig-gnutls | 186 +++++++++++++++++----
.../register-autoscan-correctly.patch | 51 ------
.../wpa-supplicant/wpa-supplicant_2.0.bb | 6 -
.../wpa-supplicant/wpa-supplicant_2.1.bb | 2 +
9 files changed, 174 insertions(+), 105 deletions(-)
delete mode 100644 meta/recipes-connectivity/bluez5/bluez5_5.14.bb
create mode 100644 meta/recipes-connectivity/bluez5/bluez5_5.15.bb
rename meta/recipes-connectivity/telepathy/{telepathy-glib_0.23.0.bb => telepathy-glib_0.23.2.bb} (76%)
rename meta/recipes-connectivity/telepathy/{telepathy-mission-control_5.16.0.bb => telepathy-mission-control_5.16.1.bb} (89%)
rename meta/recipes-connectivity/wpa-supplicant/{wpa-supplicant-2.0.inc => wpa-supplicant.inc} (91%)
delete mode 100644 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/register-autoscan-correctly.patch
delete mode 100644 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.0.bb
create mode 100644 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.1.bb
--
1.8.3.2
next reply other threads:[~2014-02-27 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 16:07 Cristian Iorga [this message]
2014-02-27 16:07 ` [PATCH 1/4] wpa-supplicant: upgrade to 2.1 Cristian Iorga
2014-02-27 16:07 ` [PATCH 2/4] bluez5: upgrade to 5.15 Cristian Iorga
2014-02-27 16:07 ` [PATCH 3/4] telepathy-glib: upgrade to 0.23.2 Cristian Iorga
2014-02-27 16:07 ` [PATCH 4/4] telepathy-mission-control: upgrade to 5.16.1 Cristian Iorga
-- strict thread matches above, loose matches on Subject: below --
2014-08-27 18:10 [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.1393517205.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