Received-SPF: pass (google.com: domain of linux-kernel+bounces-214273-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] platform/chrome: cros_ec_lpc: Handle zero length read/write
From: patchwork-bot+chrome-platform@kernel.org
Message-Id: 
 <171833343030.26166.18265568049906773511.git-patchwork-notify@kernel.org>
Date: Fri, 14 Jun 2024 02:50:30 +0000
References: <20240613212542.403-1-ben@jubnut.com>
In-Reply-To: <20240613212542.403-1-ben@jubnut.com>
To: Ben Walsh <ben@jubnut.com>
Cc: dan.carpenter@linaro.org, bleung@chromium.org, tzungbi@kernel.org,
 groeck@chromium.org, chrome-platform@lists.linux.dev,
 linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org

Hello:

This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:

On Thu, 13 Jun 2024 22:25:42 +0100 you wrote:
> cros_ec_lpc_mec_read_bytes and cros_ec_lpc_mec_write_bytes call
> cros_ec_lpc_mec_in_range, which checks if addresses are in the MEC
> address range, and returns -EINVAL if the range given is not sensible.
> 
> However cros_ec_lpc_mec_in_range was also returning -EINVAL for a zero
> length range.
> 
> [...]

Here is the summary with links:
  - platform/chrome: cros_ec_lpc: Handle zero length read/write
    https://git.kernel.org/chrome-platform/c/b57cd5703a16

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