From: Jinwang Li <jinwang.li@oss.qualcomm.com>
To: linux-bluetooth@vger.kernel.org
Cc: cheng.jiang@oss.qualcomm.com, quic_chezhou@quicinc.com,
wei.deng@oss.qualcomm.com, shuai.zhang@oss.qualcomm.com,
mengshi.wu@oss.qualcomm.com, jinwang.li@oss.qualcomm.com,
xiuzhuo.shang@oss.qualcomm.com
Subject: [PATCH v2 0/2] obexd/pbap: Fix NewMissedCalls reporting
Date: Tue, 27 Oct 2026 15:10:44 +0800 [thread overview]
Message-ID: <20261027071046.2272116-1-jinwang.li@oss.qualcomm.com> (raw)
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.
Changes in v2:
- Fix checkpatch LONG_LINE warning.
- Link to v1:
https://lore.kernel.org/all/20261026131504.1016687-1-jinwang.li@oss.qualcomm.com/
Jinwang Li (2):
obexd/pbap: Fix NewMissedCalls parameter size
obexd/pbap: Report NewMissedCalls for mch
obexd/plugins/irmc.c | 4 ++--
obexd/plugins/pbap.c | 8 ++++----
obexd/plugins/phonebook-dummy.c | 23 ++++++++++++++++++++++-
obexd/plugins/phonebook-tracker.c | 2 +-
obexd/plugins/phonebook.h | 2 +-
5 files changed, 30 insertions(+), 9 deletions(-)
--
2.34.1
next reply other threads:[~2026-10-27 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 7:10 Jinwang Li [this message]
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 ` [PATCH v2 0/2] obexd/pbap: Fix NewMissedCalls reporting patchwork-bot+bluetooth
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=20261027071046.2272116-1-jinwang.li@oss.qualcomm.com \
--to=jinwang.li@oss.qualcomm.com \
--cc=cheng.jiang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox