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] shared/vcp: Fix notification endianness
Date: Mon, 11 Dec 2023 18:40:24 +0000 [thread overview]
Message-ID: <170232002480.25763.12600598782695945445.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231211171135.437354-1-luiz.dentz@gmail.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 11 Dec 2023 12:11:35 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> 4db4d5fa1c4f ("shared/vcp: Fix endianness errors") does attempt to fix
> the endianness of stored volume offset but in the process it broke the
> notification since the value is no longer stored in the Bluetooth byte
> order (Little Endian) but instead in the cpu byte order which is then
> used in the notification as is, to fix this instead of notifying using
> the stored value it now uses a dedicated variable which does use the
> value from the request itself.
>
> [...]
Here is the summary with links:
- [BlueZ,v1] shared/vcp: Fix notification endianness
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=95838efc07d3
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-12-11 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 17:11 [PATCH BlueZ v1] shared/vcp: Fix notification endianness Luiz Augusto von Dentz
2023-12-11 18:28 ` [BlueZ,v1] " bluez.test.bot
2023-12-11 18: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=170232002480.25763.12600598782695945445.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.