linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] shared/bap: fix setting io on linked stream
Date: Mon, 11 Mar 2024 19:39:24 +0000	[thread overview]
Message-ID: <171018596458.1144.2556648186900706094.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <09755693e7900757286d3dc9fd181f8591c21a19.1710099560.git.pav@iki.fi>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Sun, 10 Mar 2024 21:40:33 +0200 you wrote:
> Fix the second bap_stream_set_io call to set the io on the linked
> transport, as it's clearly meant to.
> 
> Fixes sending duplicate stream stop/start requests.
> 
> bluetoothd[588207]: < ACL Data TX: Handle 2048 flags 0x00 dlen 11   #492 [hci1]
>       ATT: Write Command (0x52) len 6
>         Handle: 0x0098 Type: ASE Control Point (0x2bc6)
>           Data: 04020505
>             Opcode: Receiver Start Ready (0x04)
>             Number of ASE(s): 2
>             ASE: #0
>             ASE ID: 0x05
>             ASE: #1
>             ASE ID: 0x05
> 
> [...]

Here is the summary with links:
  - [BlueZ] shared/bap: fix setting io on linked stream
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c9dddb642663

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



      parent reply	other threads:[~2024-03-11 19:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10 19:40 [PATCH BlueZ] shared/bap: fix setting io on linked stream Pauli Virtanen
2024-03-10 21:37 ` [BlueZ] " bluez.test.bot
2024-03-11 19:39 ` 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=171018596458.1144.2556648186900706094.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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;
as well as URLs for NNTP newsgroup(s).