From: patchwork-bot+bluetooth@kernel.org
To: Mengshi Wu <mengshi.wu@oss.qualcomm.com>
Cc: linux-bluetooth@vger.kernel.org, shuai.zhang@oss.qualcomm.com,
cheng.jiang@oss.qualcomm.com, chezhou@qti.qualcomm.com,
wei.deng@oss.qualcomm.com, yiboz@qti.qualcomm.com,
jinwang.li@oss.qualcomm.com
Subject: Re: [PATCH v1] src/device: Fix stored gatt cache DB Hash value not update
Date: Wed, 01 Apr 2026 14:30:05 +0000 [thread overview]
Message-ID: <177505380578.3303791.15895652640205896491.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260401113930.1430598-1-mengshi.wu@oss.qualcomm.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 1 Apr 2026 19:39:30 +0800 you wrote:
> There is an asymmetry in behavior: when services are added during
> the same connection (via Service Changed indication), the persistent
> storage (disk) is not updated with the new DB hash, but when services
> are removed, it is updated.
>
> During the same connection, We check DB hash value stored at
> /var/lib/bluetooth/<adaptor addr>/cache/<remote addr>.
> When established connection, the stored DB Hash value is A.Then we
> add new services, the stored DB Hash value is still A which should
> change to B. However, if we remove the existing services, the stored
> DB Hash value changed to C.
>
> [...]
Here is the summary with links:
- [v1] src/device: Fix stored gatt cache DB Hash value not update
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0fd01e98cf94
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:[~2026-04-01 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 11:39 [PATCH v1] src/device: Fix stored gatt cache DB Hash value not update Mengshi Wu
2026-04-01 12:57 ` [v1] " bluez.test.bot
2026-04-01 14: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=177505380578.3303791.15895652640205896491.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=chezhou@qti.qualcomm.com \
--cc=jinwang.li@oss.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mengshi.wu@oss.qualcomm.com \
--cc=shuai.zhang@oss.qualcomm.com \
--cc=wei.deng@oss.qualcomm.com \
--cc=yiboz@qti.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