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 0/2] bearer: Fix auto-connect handling of LE Connect and Disconnect
Date: Mon, 09 Nov 2026 16:00:33 +0000 [thread overview]
Message-ID: <179424003399.3335769.13828179370784941457.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261107015649.84892-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 Fri, 6 Nov 2026 17:56:47 -0800 you wrote:
> org.bluez.Bearer.LE1.Disconnect is documented, like
> org.bluez.Device1.Disconnect, to disable incoming connections of a
> device that is not trusted until Connect is called again. Device1 does
> this by taking the device out of the auto-connect list, but the LE
> bearer does not: a paired HID device that is not trusted and keeps
> advertising is connected back right after Bearer.LE1.Disconnect.
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] device: Add functions to pause and resume auto-connect
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=00a473e0ada7
- [BlueZ,2/2] bearer: Fix LE Connect and Disconnect ignoring auto-connect
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=77afa9ee44ed
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-11-09 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 1:56 [PATCH BlueZ 0/2] bearer: Fix auto-connect handling of LE Connect and Disconnect Kevin Dewald
2026-11-07 1:56 ` [PATCH BlueZ 1/2] device: Add functions to pause and resume auto-connect Kevin Dewald
2026-11-07 8:43 ` bearer: Fix auto-connect handling of LE Connect and Disconnect bluez.test.bot
2026-11-07 1:56 ` [PATCH BlueZ 2/2] bearer: Fix LE Connect and Disconnect ignoring auto-connect Kevin Dewald
2026-11-09 16: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=179424003399.3335769.13828179370784941457.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 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.