Linux bluetooth development
 help / color / mirror / Atom feed
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/3] Promote the bearer interfaces to stable
Date: Mon, 26 Oct 2026 21:40:10 +0000	[thread overview]
Message-ID: <179305081006.3403508.881301264378000551.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261023223708.76232-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, 23 Oct 2026 15:37:05 -0700 you wrote:
> As offered in the Role series, this marks org.bluez.Bearer.LE1 and
> org.bluez.Bearer.BREDR1 stable, now that test/functional/test_bearer.py
> covers them.
> 
> The bearer interfaces are the only way to connect a given bearer of a
> dual-mode device. Device1.Connect picks one, by default the last used,
> so an application that only uses LE, such as a GATT library, can end
> up with only BR/EDR connected, and Device1.Connected does not say which
> bearer is up. Today such an application has to ask its users to run
> bluetoothd with --experimental.
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/3] org.bluez.Bearer: Promote to stable
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=892d1885af48
  - [BlueZ,2/3] bearer: Promote to stable
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b25019027d3b
  - [BlueZ,3/3] test: functional: run bearer tests without experimental
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b0bf49270d44

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-26 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 22:37 [PATCH BlueZ 0/3] Promote the bearer interfaces to stable Kevin Dewald
2026-10-23 22:37 ` [PATCH BlueZ 1/3] org.bluez.Bearer: Promote " Kevin Dewald
2026-10-24  1:14   ` Promote the bearer interfaces " bluez.test.bot
2026-10-23 22:37 ` [PATCH BlueZ 2/3] bearer: Promote " Kevin Dewald
2026-10-23 22:37 ` [PATCH BlueZ 3/3] test: functional: run bearer tests without experimental Kevin Dewald
2026-10-26 21:40 ` 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=179305081006.3403508.881301264378000551.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