From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bluez5_utils: fix build of gatttool
Date: Mon, 1 May 2017 09:21:42 +0200 [thread overview]
Message-ID: <20170501092142.216bc5b9@free-electrons.com> (raw)
In-Reply-To: <813b44550d7406827f9307514a8386b4462b854d.1493620107.git.baruch@tkos.co.il>
Hello,
On Mon, 1 May 2017 09:28:27 +0300, Baruch Siach wrote:
> Since BlueZ 5.44 gatttool is hidden behind the --enable-deprecated configure
> option.
>
> Also, update the help text with the new status of gatttool.
>
> Fixes:
> http://autobuild.buildroot.net/results/ddb/ddb975c9e1475fee1da63cb21240d8d59b161076/
> http://autobuild.buildroot.net/results/19a/19adc0aa5a7e48119ef4ba25ba0403867f74f678/
> http://autobuild.buildroot.net/results/9bd/9bd8e13ddffdd0631ddca30ec40cc4664729b0cb/
>
> Cc: Marcin Bis <marcin@bis.org.pl>
> Cc: Bernd Kuhls <bernd.kuhls@t-online.de>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
We have lots of patches pending on bluez5_utils, to solve this issue
and others. It's not clear what is the overall plan, as all the patches
have been sent separately (i.e not in a series).
See
https://patchwork.ozlabs.org/project/buildroot/list/?submitter=&state=&q=bluez&archive=&delegate=.
Essentially, your patch is the third one to solve the gattool problem.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-01 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 6:28 [Buildroot] [PATCH] bluez5_utils: fix build of gatttool Baruch Siach
2017-05-01 7:21 ` Thomas Petazzoni [this message]
2017-05-01 7:38 ` Baruch Siach
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=20170501092142.216bc5b9@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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