From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1] client: Fix transport.acquire auto not working as initiator
Date: Thu, 04 Dec 2025 16:00:07 +0000 [thread overview]
Message-ID: <176486400793.832454.1631055037045046996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251202201810.2022976-1-luiz.dentz@gmail.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 2 Dec 2025 15:18:10 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> Transports configured as client/initiator do not transit to
> State:pending since that is used to indicate that a stream has been
> configured and has to be accepted, when acting as initiator role
> SelectProperties/SelectConfiguration can used to indicate that
> endpoint stream configuration has been initiated locally so use that
> to mark endpoint to auto configure if that has been set.
>
> [...]
Here is the summary with links:
- [BlueZ,v1] client: Fix transport.acquire auto not working as initiator
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d383c81f848d
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:[~2025-12-04 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 20:18 [PATCH BlueZ v1] client: Fix transport.acquire auto not working as initiator Luiz Augusto von Dentz
2025-12-02 21:13 ` [BlueZ,v1] " bluez.test.bot
2025-12-04 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=176486400793.832454.1631055037045046996.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.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