Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Cristian Iorga <cristian.iorga@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/5] bluez4: update to ver. 4.101
Date: Wed,  4 Jul 2012 14:34:00 +0300	[thread overview]
Message-ID: <1341401643-4395-3-git-send-email-cristian.iorga@intel.com> (raw)
In-Reply-To: <1341401643-4395-1-git-send-email-cristian.iorga@intel.com>

Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
---
 .../{bluez4-4.99 => bluez4-4.101}/bluetooth.conf   |    0
 .../{bluez4-4.99 => bluez4-4.101}/sbc_mmx.patch    |    0
 .../bluez/{bluez4_4.99.bb => bluez4_4.101.bb}      |    9 ++++-----
 3 files changed, 4 insertions(+), 5 deletions(-)
 rename meta/recipes-connectivity/bluez/{bluez4-4.99 => bluez4-4.101}/bluetooth.conf (100%)
 rename meta/recipes-connectivity/bluez/{bluez4-4.99 => bluez4-4.101}/sbc_mmx.patch (100%)
 rename meta/recipes-connectivity/bluez/{bluez4_4.99.bb => bluez4_4.101.bb} (83%)

diff --git a/meta/recipes-connectivity/bluez/bluez4-4.99/bluetooth.conf b/meta/recipes-connectivity/bluez/bluez4-4.101/bluetooth.conf
similarity index 100%
rename from meta/recipes-connectivity/bluez/bluez4-4.99/bluetooth.conf
rename to meta/recipes-connectivity/bluez/bluez4-4.101/bluetooth.conf
diff --git a/meta/recipes-connectivity/bluez/bluez4-4.99/sbc_mmx.patch b/meta/recipes-connectivity/bluez/bluez4-4.101/sbc_mmx.patch
similarity index 100%
rename from meta/recipes-connectivity/bluez/bluez4-4.99/sbc_mmx.patch
rename to meta/recipes-connectivity/bluez/bluez4-4.101/sbc_mmx.patch
diff --git a/meta/recipes-connectivity/bluez/bluez4_4.99.bb b/meta/recipes-connectivity/bluez/bluez4_4.101.bb
similarity index 83%
rename from meta/recipes-connectivity/bluez/bluez4_4.99.bb
rename to meta/recipes-connectivity/bluez/bluez4_4.101.bb
index 32831e7..a2ba66f 100644
--- a/meta/recipes-connectivity/bluez/bluez4_4.99.bb
+++ b/meta/recipes-connectivity/bluez/bluez4_4.101.bb
@@ -1,13 +1,12 @@
 require bluez4.inc
 
-PR = "r2"
+PR = "r0"
 
 SRC_URI += "file://bluetooth.conf \
-            file://sbc_mmx.patch \
-           "
+            file://sbc_mmx.patch"
 
-SRC_URI[md5sum] = "570aa10692ed890aa0a4297b37824912"
-SRC_URI[sha256sum] = "d884b9aa5d3d9653c076b7646ca14a3e43eb84bccfe8193c49690f802bbd827c"
+SRC_URI[md5sum] = "fb42cb7038c380eb0e2fa208987c96ad"
+SRC_URI[sha256sum] = "59738410ade9f0e61a13c0f77d9aaffaafe49ba9418107e4ad75fe52846f7487"
 
 do_install_append() {
 	install -m 0644 ${S}/audio/audio.conf ${D}/${sysconfdir}/bluetooth/
-- 
1.7.9.5




  parent reply	other threads:[~2012-07-04 11:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 11:33 [PATCH 0/5] Comm and Multimedia package updates, 5 pkg Cristian Iorga
2012-07-04 11:33 ` [PATCH 1/5] telepathy-glib: update to ver. 0.19.2 Cristian Iorga
2012-07-04 11:34 ` Cristian Iorga [this message]
2012-07-09  9:07   ` [PATCH 2/5] bluez4: update to ver. 4.101 Stefan Herbrechtsmeier
2012-07-04 11:34 ` [PATCH 3/5] netbase: update to ver. 5.0 Cristian Iorga
2012-07-04 11:34 ` [PATCH 4/5] gst-plugin-bluetooth: update to ver. 4.101 Cristian Iorga
2012-07-04 11:34 ` [PATCH 5/5] ofono: update to ver. 1.8 Cristian Iorga
2012-07-05 17:16 ` [PATCH 0/5] Comm and Multimedia package updates, 5 pkg Saul Wold

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=1341401643-4395-3-git-send-email-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