From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 847323: unit/test-hfp: Re-order TS tests in alphabetical o...
Date: Mon, 01 Sep 2025 08:56:10 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/997681/000000-29795b@github.com> (raw)
Branch: refs/heads/997681
Home: https://github.com/bluez/bluez
Commit: 847323f70e29504e86033868817be706bfaa3101
https://github.com/bluez/bluez/commit/847323f70e29504e86033868817be706bfaa3101
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-09-01 (Mon, 01 Sep 2025)
Changed paths:
M unit/test-hfp.c
Log Message:
-----------
unit/test-hfp: Re-order TS tests in alphabetical order
This will simplify when looking for a test.
Commit: a562adcb7fd8d22b877eb8ee8fcb9b3e3beedef3
https://github.com/bluez/bluez/commit/a562adcb7fd8d22b877eb8ee8fcb9b3e3beedef3
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-09-01 (Mon, 01 Sep 2025)
Changed paths:
M src/shared/hfp.c
M src/shared/hfp.h
Log Message:
-----------
shared/hfp: Fix typos
Commit: 29795be67c8a5511fb8eff1f40ce18d8c531554f
https://github.com/bluez/bluez/commit/29795be67c8a5511fb8eff1f40ce18d8c531554f
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-09-01 (Mon, 01 Sep 2025)
Changed paths:
M unit/test-hfp.c
Log Message:
-----------
unit/test-hfp: Play PDUs up to the last one for HF tests
This will allows to create PDU set for TS tests which may end with
events not triggering actions, e.g. when receiving +CIEV:<callsetup>,0
where call status has already been updated by +CIEV:<call>,1
Free context->data only after completing hfp_*_unref calls.
Compare: https://github.com/bluez/bluez/compare/847323f70e29%5E...29795be67c8a
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-09-01 15:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/997681/000000-29795b@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).