From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1 1/2] test-micp: Fix endianess error
Date: Wed, 29 Nov 2023 22:40:25 +0000 [thread overview]
Message-ID: <170129762553.11308.10417535236170396199.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231129163041.2075184-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 29 Nov 2023 11:30:39 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> 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
>
> [...]
Here is the summary with links:
- [BlueZ,v1,1/2] test-micp: Fix endianess error
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3a2d3b31a3b5
- [BlueZ,v1,2/2] shared/vcp: Fix endianess errors
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4db4d5fa1c4f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-11-29 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 16:30 [PATCH BlueZ v1 1/2] test-micp: Fix endianess error Luiz Augusto von Dentz
2023-11-29 16:30 ` [PATCH BlueZ v1 2/2] shared/vcp: Fix endianess errors Luiz Augusto von Dentz
2023-11-29 17:37 ` [BlueZ,v1,1/2] test-micp: Fix endianess error bluez.test.bot
2023-11-29 22:40 ` patchwork-bot+bluetooth [this message]
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=170129762553.11308.10417535236170396199.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 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.