Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] platform/chrome: cros_typec_vdm: Fix VDO copy
From:   patchwork-bot+chrome-platform@kernel.org
Message-Id: <167476261684.7258.3064074996679774855.git-patchwork-notify@kernel.org>
Date:   Thu, 26 Jan 2023 19:50:16 +0000
References: <20230113182626.1149539-1-pmalani@chromium.org>
In-Reply-To: <20230113182626.1149539-1-pmalani@chromium.org>
To:     Prashant Malani <pmalani@chromium.org>
Cc:     linux-kernel@vger.kernel.org, chrome-platform@lists.linux.dev,
        bleung@chromium.org
Precedence: bulk

Hello:

This patch was applied to chrome-platform/linux.git (for-next)
by Prashant Malani <pmalani@chromium.org>:

On Fri, 13 Jan 2023 18:26:26 +0000 you wrote:
> The usage of memcpy() affects the representation of the VDOs as they are
> copied to the EC Host Command buffer. Specifically, all higher order
> bits get dropped (for example: a VDO of 0x406 just gets copied as 0x6).
> 
> Avoid this by explicitly copying each VDO in the array. The number of
> VDOs generated by alternate mode drivers in their VDMs is almost always
> just 1 (apart from the header) so this doesn't affect performance in a
> meaningful way).
> 
> [...]

Here is the summary with links:
  - platform/chrome: cros_typec_vdm: Fix VDO copy
    https://git.kernel.org/chrome-platform/c/478f32ab4daa

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html