From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 3a2d3b: test-micp: Fix endianness error
Date: Wed, 29 Nov 2023 14:38:03 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/bd5342-4db4d5@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 3a2d3b31a3b5a7eeb45952ce880ca58c93b985bb
https://github.com/bluez/bluez/commit/3a2d3b31a3b5a7eeb45952ce880ca58c93b985bb
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2023-11-29 (Wed, 29 Nov 2023)
Changed paths:
M unit/test-micp.c
Log Message:
-----------
test-micp: Fix endianness error
On big endian the followin error can be observed:
MICP/CL/CGGIT/SER/BV-01-C - init
MICP/CL/CGGIT/SER/BV-01-C - setup
MICP/CL/CGGIT/SER/BV-01-C - setup complete
MICP/CL/CGGIT/SER/BV-01-C - run
micp_write_value handle: 3
**
ERROR:src/shared/tester.c:954:test_io_recv: assertion failed:
(memcmp(buf, iov->iov_base, len) == 0)
Bail out! ERROR:src/shared/tester.c:954:test_io_recv: assertion failed:
(memcmp(buf, iov->iov_base, len) == 0)
Aborted
Commit: 4db4d5fa1c4fefcf3ec7f161a4c7164df0195ed7
https://github.com/bluez/bluez/commit/4db4d5fa1c4fefcf3ec7f161a4c7164df0195ed7
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2023-11-29 (Wed, 29 Nov 2023)
Changed paths:
M src/shared/vcp.c
Log Message:
-----------
shared/vcp: Fix endianness errors
On big endian the followin error can be observed:
VOCS/SR/SGGIT/CHA/BV-02-C - init
VOCS/SR/SGGIT/CHA/BV-02-C - setup
VOCS/SR/SGGIT/CHA/BV-02-C - setup complete
VOCS/SR/SGGIT/CHA/BV-02-C - run
**
ERROR:src/shared/tester.c:954:test_io_recv: assertion failed:
(memcmp(buf, iov->iov_base, len) == 0)
Bail out! ERROR:src/shared/tester.c:954:test_io_recv: assertion failed:
(memcmp(buf, iov->iov_base, len) == 0)
Aborted
Compare: https://github.com/bluez/bluez/compare/bd5342fdf46a...4db4d5fa1c4f
reply other threads:[~2023-11-29 22:38 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/bd5342-4db4d5@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.