All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3] [wrynose][backport] bluez5: Abort continuing response on fragmented CT replies
Date: Thu, 19 Nov 2026 11:24:57 +0100	[thread overview]
Message-ID: <DMZ44U8O2RR3.3PG16IJMUE4A7@smile.fr> (raw)
In-Reply-To: <a4daf280-ed05-4335-95c1-dd0f99123184@oss.qualcomm.com>

On Thu Nov 19, 2026 at 9:12 AM CET, Shuai Zhang via openembedded-core wrote:
> Hi maintainers
>
> On 11/11/2026 7:22 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 v3:
>> - Remove Simon Mikuda's Signed-off-by from the recipe patch, as he did
>>    not sign off the upstream commit
>> Link to v2: https://lists.openembedded.org/g/openembedded-core/message/248377
>>
>> Changes for v2:
>> - Fix subject prefix to [wrynose][backport]
>> - Drop Upstream-Status tag from the commit message
>> 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 | 62 +++++++++++++++++++
>>   2 files changed, 63 insertions(+)
>>   create mode 100644 meta/recipes-connectivity/bluez5/bluez5/0001-avrcp-Abort-continuing-response-on-fragmented-CT-rep.patch
>>
>
> just following up to see if there are any updates on this.
>
> Thanks,
>
> Shuai

It is part of the current review series:
https://lore.kernel.org/openembedded-core/cover.1794939400.git.yoann.congal@smile.fr/
... pending negative reviews, it should merge tomorrow.

PS: Checking if your patch is in the review series is a good reason to
read those.

Regards,
-- 
Yoann Congal
Smile ECS

      reply	other threads:[~2026-11-19 10:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 11:22 [PATCH v3] [wrynose][backport] bluez5: Abort continuing response on fragmented CT replies Shuai Zhang
2026-11-19  8:12 ` Shuai Zhang
2026-11-19 10:24   ` Yoann Congal [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=DMZ44U8O2RR3.3PG16IJMUE4A7@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 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.