From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] bluez5_utils: version bump fixes and updates
Date: Tue, 02 May 2017 18:05:38 +0300 [thread overview]
Message-ID: <1493737538.24567.274.camel@linux.intel.com> (raw)
In-Reply-To: <cover.1493643541.git.baruch@tkos.co.il>
On Mon, 2017-05-01 at 15:59 +0300, Baruch Siach wrote:
> The recent bluez5_utils version bump moved around the build options so
> that?
> some builds now fail, and the help text became incorrect. This short
> series?
> fixes some of these issues.
>
Thanks for taking care of this, I appreciate.
I have no time to keep on it right now, so, feel free modify as it
satisfies Thomas and others.
On first glance what you did looks sane to me.
> This series is mostly based on Andy Shevchenko's patch[1] with the
> following?
> main changes:
>
> ? * Split out the DEPRECATED handling, adding a fix to the gatttool
> build?
> ????issue in the process
>
> ? * Remove the redundant BR2_PACKAGE_BLUEZ5_UTILS_GATTTOOL config
> option
>
> ? * Split the option addition patch into two: one for options that
> were?
> ????previously under --enable-experimental, and one for the newly
> introduced?
> ????midi profile
>
> ? * Add missing BR2_PACKAGE_ALSA_LIB_SEQ select
>
> [1] https://patchwork.ozlabs.org/patch/741645/
>
> Andy Shevchenko (2):
> ? bluez5_utils: allow enabling formerly experimental plugins
> ? bluez5_utils: allow building the midi profile
>
> Baruch Siach (2):
> ? bluez5_utils: allow install of deprecated tools
> ? bluez5_utils: correct the experimental option text
>
> ?Config.in.legacy?????????????????????|??9 +++++++++
> ?package/bluez5_utils/Config.in???????| 39
> +++++++++++++++++++++++++++---------
> ?package/bluez5_utils/bluez5_utils.mk | 34
> ++++++++++++++++++++++++++++++-
> ?3 files changed, 71 insertions(+), 11 deletions(-)
>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2017-05-02 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 12:59 [Buildroot] [PATCH 0/4] bluez5_utils: version bump fixes and updates Baruch Siach
2017-05-01 12:59 ` [Buildroot] [PATCH 1/4] bluez5_utils: allow install of deprecated tools Baruch Siach
2017-05-01 14:57 ` Thomas Petazzoni
2017-05-01 15:09 ` Baruch Siach
2017-05-05 12:32 ` Peter Korsgaard
2017-05-01 12:59 ` [Buildroot] [PATCH 2/4] bluez5_utils: correct the experimental option text Baruch Siach
2017-05-05 12:37 ` Peter Korsgaard
2017-05-01 12:59 ` [Buildroot] [PATCH 3/4] bluez5_utils: allow enabling formerly experimental plugins Baruch Siach
2017-05-05 12:37 ` Peter Korsgaard
2017-05-01 12:59 ` [Buildroot] [PATCH 4/4] bluez5_utils: allow building the midi profile Baruch Siach
2017-05-05 12:37 ` Peter Korsgaard
2017-05-02 15:05 ` Andy Shevchenko [this message]
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=1493737538.24567.274.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=buildroot@busybox.net \
/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