From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: ISO: Fix getname not returning broadcast fields
Date: Thu, 24 Jul 2025 21:00:09 +0000 [thread overview]
Message-ID: <175339080999.2527392.10645228008182771222.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250724205259.13273-2-luiz.dentz@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 24 Jul 2025 16:52:59 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> getname shall return iso_bc fields for both BIS_LINK and PA_LINK since
> the likes of bluetoothd do use the getpeername to retrieve the SID both
> when enumerating the broadcasters and when synchronizing.
>
> Fixes: a7bcffc673de ("Bluetooth: Add PA_LINK to distinguish BIG sync and PA sync connections")
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: ISO: Fix getname not returning broadcast fields
https://git.kernel.org/bluetooth/bluetooth-next/c/05f7f9433718
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-07-24 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 20:52 [PATCH v1] Bluetooth: hci_sync: Fix scan state after PA Sync has been established Luiz Augusto von Dentz
2025-07-24 20:52 ` [PATCH v1] Bluetooth: ISO: Fix getname not returning broadcast fields Luiz Augusto von Dentz
2025-07-24 21:00 ` patchwork-bot+bluetooth [this message]
2025-07-24 21:00 ` [PATCH v1] Bluetooth: hci_sync: Fix scan state after PA Sync has been established patchwork-bot+bluetooth
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=175339080999.2527392.10645228008182771222.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 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.