From: patchwork-bot+bluetooth@kernel.org
To: Jinwang Li <jinwang.li@oss.qualcomm.com>
Cc: linux-bluetooth@vger.kernel.org, cheng.jiang@oss.qualcomm.com,
quic_chezhou@quicinc.com, wei.deng@oss.qualcomm.com,
shuai.zhang@oss.qualcomm.com, mengshi.wu@oss.qualcomm.com,
xiuzhuo.shang@oss.qualcomm.com
Subject: Re: [PATCH v2 0/2] obexd/pbap: Fix NewMissedCalls reporting
Date: Wed, 28 Oct 2026 13:30:11 +0000 [thread overview]
Message-ID: <179319421156.722681.17373470691534809442.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261027071046.2272116-1-jinwang.li@oss.qualcomm.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 27 Oct 2026 15:10:44 +0800 you wrote:
> This series fixes NewMissedCalls reporting in obexd PBAP.
>
> The first patch fixes the apparam encoding: NewMissedCalls is a
> one-byte value but was encoded as uint16. The second patch makes the
> dummy backend report the actual missed-call count for the mch folder
> instead of always zero, which is required by PTS PBAP/PSE/PBD/BV-05-C.
>
> [...]
Here is the summary with links:
- [v2,1/2] obexd/pbap: Fix NewMissedCalls parameter size
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f1af76b9868e
- [v2,2/2] obexd/pbap: Report NewMissedCalls for mch
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d987dbc0f081
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-10-28 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 7:10 [PATCH v2 0/2] obexd/pbap: Fix NewMissedCalls reporting Jinwang Li
2026-10-27 7:10 ` [PATCH v2 1/2] obexd/pbap: Fix NewMissedCalls parameter size Jinwang Li
2026-10-27 9:01 ` obexd/pbap: Fix NewMissedCalls reporting bluez.test.bot
2026-10-27 7:10 ` [PATCH v2 2/2] obexd/pbap: Report NewMissedCalls for mch Jinwang Li
2026-10-28 13: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=179319421156.722681.17373470691534809442.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=jinwang.li@oss.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mengshi.wu@oss.qualcomm.com \
--cc=quic_chezhou@quicinc.com \
--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.