Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-534-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH BlueZ v1] shared/vcp: Fix notification endianness
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <170232002480.25763.12600598782695945445.git-patchwork-notify@kernel.org>
Date: Mon, 11 Dec 2023 18:40:24 +0000
References: <20231211171135.437354-1-luiz.dentz@gmail.com>
In-Reply-To: <20231211171135.437354-1-luiz.dentz@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org

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