From: Denis OSTERLAND <denis.osterland@diehl.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] bluez: version bump 5.50 -> 5.51
Date: Thu, 10 Oct 2019 11:48:59 +0000 [thread overview]
Message-ID: <54f42c5d8e9d688781cbbd03a7cb3fc956aac37a.camel@diehl.com> (raw)
In-Reply-To: <1570579882-29911-1-git-send-email-apr@cn-eng.de>
Hi,
I used btmon, bluetoothd, bluetoothctl and btattach to perform a scan.
This works as well. Another quick test ;-)
Regards Denis
Am Mittwoch, den 09.10.2019, 02:11 +0200 schrieb Andreas Pretzsch:
> Update BlueZ 5.50 (Jun 2018) to BlueZ 5.51 (Sep 2019).
>
> Quoting the announcement: "There are too many fixes to cover them in
> the release announcement, but feature-wise the two notable things are
> improved Bluetooth Mesh support as well as support for the GATT
> Database Hash feature."
>
> There are no relevant new configure options.
> Explicitly set the new configure option "external-ell" to disabled.
> It is connected to mesh and/or btpclient, which are already both
> explicitly disabled. In this context, order them together.
> The now settable "runstatedir" (default LOCALSTATEDIR/run) should be fine.
>
> There are new test programs "test-mesh" and "agent.py".
> Install them like the rest, if enabled. Both python with shebang.
> While at it, fix the double-install of the python scripts, with and
> without executable permissions. The change e6c2932 "bluez: the python
> tests have no shebang so don't make them executable" was not fully
> minded in caa56e6 "bluez: version bump 5.30 -> 5.50".
>
> There are no bluez patches, so nothing to merge.
>
> Signed-off-by: Andreas Pretzsch <apr@cn-eng.de>
> ---
> Quick test with scanning and l2ping (still) works. No further tests.
Tested-by: Denis Osterland <Denis.Osterland@diehl.com>
Diehl Connectivity Solutions GmbH
Geschäftsführung: Horst Leonberger
Sitz der Gesellschaft: Nürnberg - Registergericht: Amtsgericht
Nürnberg: HRB 32315
___________________________________________________________________________________________________
Der Inhalt der vorstehenden E-Mail ist nicht rechtlich bindend. Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Informieren Sie uns bitte, wenn Sie diese E-Mail faelschlicherweise erhalten haben. Bitte loeschen Sie in diesem Fall die Nachricht.
Jede unerlaubte Form der Reproduktion, Bekanntgabe, Aenderung, Verteilung und/oder Publikation dieser E-Mail ist strengstens untersagt.
- Informationen zum Datenschutz, insbesondere zu Ihren Rechten, erhalten Sie unter https://www.diehl.com/group/de/transparenz-und-informationspflichten/
The contents of the above mentioned e-mail is not legally binding. This e-mail contains confidential and/or legally protected information. Please inform us if you have received this e-mail by
mistake and delete it in such a case. Each unauthorized reproduction, disclosure, alteration, distribution and/or publication of this e-mail is strictly prohibited.
- For general information on data protection and your respective rights please visit https://www.diehl.com/group/en/transparency-and-information-obligations/
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-10-10 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 0:11 Andreas Pretzsch
2019-10-10 11:48 ` Denis OSTERLAND [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=54f42c5d8e9d688781cbbd03a7cb3fc956aac37a.camel@diehl.com \
--to=denis.osterland@diehl.com \
--cc=ptxdist@pengutronix.de \
/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