From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Wei Deng" <wei.deng@oss.qualcomm.com>,
<openembedded-core@lists.openembedded.org>
Cc: <cheng.jiang@oss.qualcomm.com>, <shuai.zhang@oss.qualcomm.com>,
<mengshi.wu@oss.qualcomm.com>, <jinwang.li@oss.qualcomm.com>,
<xiuzhuo.shang@oss.qualcomm.com>
Subject: Re: [PATCH 0/4] bluez5: backport fixes from master to wrynose
Date: Fri, 26 Jun 2026 10:18:52 +0200 [thread overview]
Message-ID: <DJIU0RAK8OYL.3PM31UJSJG9OJ@smile.fr> (raw)
In-Reply-To: <20260626064233.704350-1-wei.deng@oss.qualcomm.com>
On Fri Jun 26, 2026 at 8:42 AM CEST, Wei Deng wrote:
> These four patches are backports of fixes already merged in OE-core master
> that are missing from wrynose. The first three patches (fixes from Jinwang,
> Xiuzhuo and Mengshi) shift the SRC_URI context in bluez5.inc such that the
> fourth patch (OBEX IMTU fix) cannot be cherry-picked cleanly onto wrynose
> without them.
> Please add to the wrynose review series.
Hello,
Since this series is for wrynose, could you resend it with [wrynose] in
the patch titles?
Something like (adapted from the README suggestion):
git send-email -M -4 --to openembedded-core@lists.openembedded.org --subject-prefix='wrynose][PATCH'
This helps a lot to avoid losing track of patches.
Thanks!
>
> Jinwang Li (1):
> bluez5: fix set volume failure
>
> Mengshi Wu (1):
> bluez5: fix gatt cache sync issue
>
> Wei Deng (1):
> bluez5: set L2CAP IMTU for OBEX profile listeners
>
> xiuzhuo.shang@oss.qualcomm.com (1):
> bluez5: Fix sending extra bytes with MGMT_OP_ADD_EXT_ADV_DATA
>
> meta/recipes-connectivity/bluez5/bluez5.inc | 4 +
> ...sending-extra-bytes-with-MGMT_OP_ADD.patch | 33 +++++
> ...2CAP-IMTU-for-OBEX-profile-listeners.patch | 118 ++++++++++++++++++
> ...x-stored-gatt-cache-DB-Hash-value-no.patch | 84 +++++++++++++
> ...t-volume-failure-with-invalid-device.patch | 46 +++++++
> 5 files changed, 285 insertions(+)
> create mode 100644 meta/recipes-connectivity/bluez5/bluez5/0001-advertising-Fix-sending-extra-bytes-with-MGMT_OP_ADD.patch
> create mode 100644 meta/recipes-connectivity/bluez5/bluez5/0001-profile-Set-L2CAP-IMTU-for-OBEX-profile-listeners.patch
> create mode 100644 meta/recipes-connectivity/bluez5/bluez5/0001-src-device-Fix-stored-gatt-cache-DB-Hash-value-no.patch
> create mode 100644 meta/recipes-connectivity/bluez5/bluez5/0001-transport-Fix-set-volume-failure-with-invalid-device.patch
--
Yoann Congal
Smile ECS
prev parent reply other threads:[~2026-06-26 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 6:42 [PATCH 0/4] bluez5: backport fixes from master to wrynose Wei Deng
2026-06-26 6:42 ` [PATCH 1/4] bluez5: fix set volume failure Wei Deng
2026-06-26 6:42 ` [PATCH 2/4] bluez5: Fix sending extra bytes with MGMT_OP_ADD_EXT_ADV_DATA Wei Deng
2026-06-26 6:42 ` [PATCH 3/4] bluez5: fix gatt cache sync issue Wei Deng
2026-06-26 6:42 ` [PATCH 4/4] bluez5: set L2CAP IMTU for OBEX profile listeners Wei Deng
2026-06-26 8:18 ` 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=DJIU0RAK8OYL.3PM31UJSJG9OJ@smile.fr \
--to=yoann.congal@smile.fr \
--cc=cheng.jiang@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