All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter A. Bigot" <pab@pabigot.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Miscellaneous bluez patches
Date: Wed, 26 Nov 2014 13:44:56 -0600	[thread overview]
Message-ID: <cover.1417029596.git.pab@pabigot.com> (raw)

These resolve the conflict for provider of hcidump between bluez4 and
bluez5, provide a new package containing the useful tools in bluez5 that
upstream doesn't think should be installed, and provides a mechanism for
enabling the experimental features such as the new GATT interface.

The following changes since commit ab63640fad50954b0440ab107c96dbd3f919ea4d:

  gdk-pixbuf: use ptest-gnome (2014-11-25 13:03:30 +0000)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib pabigot/bluez5
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=pabigot/bluez5

Peter A. Bigot (3):
  bluez-hcidump: select provider as bluez4 or bluez5
  bluez5: add a package for tools left in the build area
  bluez5: support experimental through PACKAGECONFIG

 meta/conf/distro/include/default-providers.inc     |  1 +
 .../bluez/bluez-hcidump_2.5.bb                     |  2 +
 meta/recipes-connectivity/bluez5/bluez5.inc        | 29 +++++++++++++-
 meta/recipes-connectivity/bluez5/bluez5_5.25.bb    | 46 ++++++++++++++++++++++
 4 files changed, 77 insertions(+), 1 deletion(-)

-- 
1.8.5.5



             reply	other threads:[~2014-11-26 19:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 19:44 Peter A. Bigot [this message]
2014-11-26 19:44 ` [PATCH 1/3] bluez-hcidump: select provider as bluez4 or bluez5 Peter A. Bigot
2014-11-26 19:44 ` [PATCH 2/3] bluez5: add a package for tools left in the build area Peter A. Bigot
2014-11-26 19:44 ` [PATCH 3/3] bluez5: support experimental through PACKAGECONFIG Peter A. Bigot
2014-12-05  0:30 ` [PATCH 0/3] Miscellaneous bluez patches Peter A. Bigot
2014-12-05 23:13   ` Burton, Ross

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.1417029596.git.pab@pabigot.com \
    --to=pab@pabigot.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.