From: "Yoann Congal" <yoann.congal@smile.fr>
To: <shuai.zhang@oss.qualcomm.com>,
<openembedded-core@lists.openembedded.org>
Cc: <cheng.jiang@oss.qualcomm.com>, <wei.deng@oss.qualcomm.com>,
<mengshi.wu@oss.qualcomm.com>, <jinwang.li@oss.qualcomm.com>,
<xiuzhuo.shang@oss.qualcomm.com>,
<chenhong.zhou@oss.qualcomm.com>
Subject: Re: [OE-core] [PATCH v2] [wrynose][backport] bluez5: Abort continuing response on fragmented CT replies
Date: Tue, 27 Oct 2026 09:44:04 +0100 [thread overview]
Message-ID: <DMFHL2HT2BNT.9OO9PUN4ME6Z@smile.fr> (raw)
In-Reply-To: <75823d78-77f7-4c1e-ab72-147fbc1130cb@oss.qualcomm.com>
On Tue Oct 27, 2026 at 8:22 AM CET, Shuai Zhang via lists.openembedded.org wrote:
> Hi Maintainer,
>
> On 10/21/2026 5:00 PM, Shuai Zhang wrote:
>> Send AbortContinuingResponse when a Get Element Attributes reply
>> arrives fragmented, as the CT side does not reassemble fragments.
>>
>> Backport upstream bluez commit 249e2bedf ("avrcp: Abort continuing
>> response on fragmented CT replies") to bluez 5.86.
>>
>> Fixes PTS test AVRCP/CT/RCR/BV-03-C.
>>
>> Signed-off-by: Shuai Zhang <shuai.zhang@oss.qualcomm.com>
>> ---
>> Changes for v2:
>> - Fix subject prefix to [wrynose][backport]
>> - Drop Upstream-Status tag from the commit message
>> - Keep upstream Upstream-Status and both Signed-off-by lines in the recipe patch
>>
>> Link to v1: https://lists.openembedded.org/g/openembedded-core/topic/patchtest_results_for/121863269
>> ---
>> meta/recipes-connectivity/bluez5/bluez5.inc | 1 +
>> ...inuing-response-on-fragmented-CT-rep.patch | 63 +++++++++++++++++++
>> 2 files changed, 64 insertions(+)
>> create mode 100644 meta/recipes-connectivity/bluez5/bluez5/0001-avrcp-Abort-continuing-response-on-fragmented-CT-rep.patch
>
> Just wanted to check if there are any updates on this. Thanks!
Hello,
I couldn't take this for the current wrynose cycle, so, it will have to
wait until the next cycle, in 1-2 weeks.
Regards,
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-10-27 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 9:00 [PATCH v2] [wrynose][backport] bluez5: Abort continuing response on fragmented CT replies Shuai Zhang
2026-10-27 7:22 ` Shuai Zhang
2026-10-27 8:44 ` Yoann Congal [this message]
2026-11-09 10:19 ` [OE-core] " Yoann Congal
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=DMFHL2HT2BNT.9OO9PUN4ME6Z@smile.fr \
--to=yoann.congal@smile.fr \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=chenhong.zhou@oss.qualcomm.com \
--cc=jinwang.li@oss.qualcomm.com \
--cc=mengshi.wu@oss.qualcomm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=shuai.zhang@oss.qualcomm.com \
--cc=wei.deng@oss.qualcomm.com \
--cc=xiuzhuo.shang@oss.qualcomm.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