From: patchwork-bot+bluetooth@kernel.org
To: Kevin Dewald <kevin@simpleble.org>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ v2 0/6] Add Connectable property to org.bluez.Device
Date: Fri, 02 Oct 2026 15:00:06 +0000 [thread overview]
Message-ID: <179095320641.3455312.4778781139268053078.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261002054618.30994-1-kevin@simpleble.org>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 1 Oct 2026 22:46:11 -0700 you wrote:
> bluetoothd records whether each advertising report was connectable,
> from the Device Found event's Not Connectable flag, and uses it
> internally, for example to pick the bearer to connect and to drop
> temporary non-connectable devices when discovery stops. Applications
> cannot read it over D-Bus, so they have to guess, e.g. from whether the
> device has a name, which is wrong for named beacons and for unnamed
> peripherals.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/6] org.bluez.Device: Add Connectable property
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=75a778e17f49
- [BlueZ,v2,2/6] org.bluez.Bearer: Add Connectable property
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f890d4b660c6
- [BlueZ,v2,3/6] device: Add Connectable property
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=6afb6e729270
- [BlueZ,v2,4/6] bearer: Add Connectable property
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ab50d5e88fb6
- [BlueZ,v2,5/6] client: Print Connectable in info
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=82f671c83429
- [BlueZ,v2,6/6] client: Print discoverable broadcasters in red
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4dc15be8ee3f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-02 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 5:46 [PATCH BlueZ v2 0/6] Add Connectable property to org.bluez.Device Kevin Dewald
2026-10-02 5:46 ` [PATCH BlueZ v2 1/6] org.bluez.Device: Add Connectable property Kevin Dewald
2026-10-02 12:16 ` Add Connectable property to org.bluez.Device bluez.test.bot
2026-10-02 5:46 ` [PATCH BlueZ v2 2/6] org.bluez.Bearer: Add Connectable property Kevin Dewald
2026-10-02 5:46 ` [PATCH BlueZ v2 3/6] device: " Kevin Dewald
2026-10-02 5:46 ` [PATCH BlueZ v2 4/6] bearer: " Kevin Dewald
2026-10-02 5:46 ` [PATCH BlueZ v2 5/6] client: Print Connectable in info Kevin Dewald
2026-10-02 5:46 ` [PATCH BlueZ v2 6/6] client: Print discoverable broadcasters in red Kevin Dewald
2026-10-02 15:00 ` patchwork-bot+bluetooth [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=179095320641.3455312.4778781139268053078.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=kevin@simpleble.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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