From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v3 0/7] audio/avrcp: Fix crash with invalid UTF-8 item name
Date: Tue, 08 Jul 2025 16:30:08 +0000 [thread overview]
Message-ID: <175199220831.4128987.12077387745459517982.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250708154308.238963-1-frederic.danis@collabora.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 8 Jul 2025 17:43:00 +0200 you wrote:
> As stated in AVRCP 1.6.2 chapter 6.10.2.3 Media element item, for the
> Displayable Name Length property, the target device may truncate the
> item name:
>
> Length of Displayable Name in octets. The name shall be limited such
> that a response to a GetFolderItems containing one media player item
> fits within the maximum size of PDU which can be received by the CT.
>
> [...]
Here is the summary with links:
- [BlueZ,v3,1/7] shared/util: Add strtoutf8 function
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0440ca68a8c4
- [BlueZ,v3,2/7] audio/avrcp: Fix crash with invalid UTF-8 item name
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=89079f2ca635
- [BlueZ,v3,3/7] audio/mcp: Use strtoutf8 for player name and track title
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a8f59849253d
- [BlueZ,v3,4/7] audio/gap: Use strtoutf8 for GAP device name
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a0387d66372b
- [BlueZ,v3,5/7] eir: Use strtoutf8 for device names
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=218db700f493
- [BlueZ,v3,6/7] shared/ad: Use strtoutf8 for name
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4cedd8d19ad5
- [BlueZ,v3,7/7] unit/test-eir: Add name encoding tests
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=004518d061d4
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-07-08 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 15:43 [PATCH BlueZ v3 0/7] audio/avrcp: Fix crash with invalid UTF-8 item name Frédéric Danis
2025-07-08 15:43 ` [PATCH BlueZ v3 1/7] shared/util: Add strtoutf8 function Frédéric Danis
2025-07-08 17:06 ` audio/avrcp: Fix crash with invalid UTF-8 item name bluez.test.bot
2025-07-08 15:43 ` [PATCH BlueZ v3 2/7] " Frédéric Danis
2025-07-08 15:43 ` [PATCH BlueZ v3 3/7] audio/mcp: Use strtoutf8 for player name and track title Frédéric Danis
2025-07-08 15:43 ` [PATCH BlueZ v3 4/7] audio/gap: Use strtoutf8 for GAP device name Frédéric Danis
2025-07-08 15:43 ` [PATCH BlueZ v3 5/7] eir: Use strtoutf8 for device names Frédéric Danis
2025-07-08 15:43 ` [PATCH BlueZ v3 6/7] shared/ad: Use strtoutf8 for name Frédéric Danis
2025-07-08 17:12 ` Pauli Virtanen
2025-07-08 17:16 ` Pauli Virtanen
2025-07-08 17:19 ` Luiz Augusto von Dentz
2025-07-08 15:43 ` [PATCH BlueZ v3 7/7] unit/test-eir: Add name encoding tests Frédéric Danis
2025-07-08 16:30 ` 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=175199220831.4128987.12077387745459517982.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
/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.