[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165044581114.11968.7352761617264023399.git-patchwork-notify@kernel.org>
Date: Wed, 20 Apr 2022 09:10:11 +0000
From: patchwork-bot+chrome-platform@...nel.org
To: Guenter Roeck <linux@...ck-us.net>
Cc: bleung@...omium.org, chrome-platform@...ts.linux.dev,
linux-kernel@...r.kernel.org, dnojiri@...omium.org,
robbarnes@...gle.com, rajatja@...gle.com, briannorris@...omium.org,
parthmalkan@...gle.com
Subject: Re: [PATCH v2] platform/chrome: Re-introduce cros_ec_cmd_xfer and use it
for ioctls
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@...nel.org>:
On Fri, 18 Mar 2022 09:54:22 -0700 you wrote:
> Commit 413dda8f2c6f ("platform/chrome: cros_ec_chardev: Use
> cros_ec_cmd_xfer_status helper") inadvertendly changed the userspace ABI.
> Previously, cros_ec ioctls would only report errors if the EC communication
> failed, and otherwise return success and the result of the EC
> communication. An EC command execution failure was reported in the EC
> response field. The above mentioned commit changed this behavior, and the
> ioctl itself would fail. This breaks userspace commands trying to analyze
> the EC command execution error since the actual EC command response is no
> longer reported to userspace.
>
> [...]
Here is the summary with links:
- [v2] platform/chrome: Re-introduce cros_ec_cmd_xfer and use it for ioctls
https://git.kernel.org/chrome-platform/c/57b888ca2541
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists