From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 825015: shared/shell: Fix not dequeueing command
Date: Mon, 26 Jan 2026 09:54:43 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/fddcda-521088@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 825015d82e2efbef08f669f146735c1f6be42583
https://github.com/bluez/bluez/commit/825015d82e2efbef08f669f146735c1f6be42583
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-01-23 (Fri, 23 Jan 2026)
Changed paths:
M src/shared/shell.c
Log Message:
-----------
shared/shell: Fix not dequeueing command
If script execution started with command that call
bt_shell_noninteractive_quit directly it wouldn't execute the next
command since data.line wouldn't be set.
Commit: 521088388babaa02deca64abf729ebae9d7f1a2b
https://github.com/bluez/bluez/commit/521088388babaa02deca64abf729ebae9d7f1a2b
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-01-26 (Mon, 26 Jan 2026)
Changed paths:
M src/shared/tmap.c
Log Message:
-----------
shared/tmap: Fix TMAP/SR/SGGIT/CHA/BV-01-C on big endian
This fix the following error cause by not converting the role value to
little endian:
TMAP/SR/SGGIT/CHA/BV-01-C [Characteristic GGIT - TMAP Role] - run
**
ERROR:src/shared/tester.c:992:test_io_recv: assertion failed: (memcmp(buf, iov->iov_base, len) == 0)
Bail out! ERROR:src/shared/tester.c:992:test_io_recv: assertion failed: (memcmp(buf, iov->iov_base, len) == 0)
Compare: https://github.com/bluez/bluez/compare/fddcda9751af...521088388bab
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-01-26 17:54 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/fddcda-521088@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 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.