From: hadess <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 44f6fb: avctp: Fix typo in comment which contradicts the c...
Date: Wed, 19 Aug 2026 12:42:32 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/5abc00-c73fa2@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 44f6fbc4e3b10582ffc5728685c9a267766eebd8
https://github.com/bluez/bluez/commit/44f6fbc4e3b10582ffc5728685c9a267766eebd8
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-08-18 (Tue, 18 Aug 2026)
Changed paths:
M profiles/audio/avctp.c
Log Message:
-----------
avctp: Fix typo in comment which contradicts the conditional below
The comment says "If the request set a callback send it directly" but
checks for whether "the request did not set a callback" using
if (!func)
Commit: 58088149872d014684a582fdb7ad01a5180c9bc5
https://github.com/bluez/bluez/commit/58088149872d014684a582fdb7ad01a5180c9bc5
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-08-19 (Wed, 19 Aug 2026)
Changed paths:
M profiles/audio/avrcp.c
Log Message:
-----------
avrcp: Fix media/folder name not being set
*namelen was used before being set.
Fixes: bd8989620ed6 ("avrcp: Fix Out-of-Bounds Read in AVRCP GetFolderItems parsing")
Commit: 1280c6f9d00a96ab2a513a347eec467fdc2ceb99
https://github.com/bluez/bluez/commit/1280c6f9d00a96ab2a513a347eec467fdc2ceb99
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-08-19 (Wed, 19 Aug 2026)
Changed paths:
M doc/test-runner.rst
Log Message:
-----------
doc: Fix typo in test-runner.rst
s/lunches/launches/
Commit: c73fa2f9ae2d366cb8a4f101fa9a5ccd9f33a4ea
https://github.com/bluez/bluez/commit/c73fa2f9ae2d366cb8a4f101fa9a5ccd9f33a4ea
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-08-19 (Wed, 19 Aug 2026)
Changed paths:
M tools/test-runner.c
Log Message:
-----------
test-runner: "-a" option also stands for "--all"
In the options for most command-line tools, -a stands for --all, and so
it does for test-runner. Add --all to the option description before
--auto as it's a more common option.
Compare: https://github.com/bluez/bluez/compare/5abc0045b84a...c73fa2f9ae2d
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-08-19 19:42 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/master/5abc00-c73fa2@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