From: patchwork-bot+chrome-platform@kernel.org
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
Subject: Re: [PATCH] platform/chrome: cros_ec_lpc: Handle zero length read/write
Date: Fri, 14 Jun 2024 02:50:30 +0000 [thread overview]
Message-ID: <171833343030.26166.18265568049906773511.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240613212542.403-1-ben@jubnut.com>
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
next prev parent reply other threads:[~2024-06-14 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 21:25 [PATCH] platform/chrome: cros_ec_lpc: Handle zero length read/write Ben Walsh
2024-06-14 2:50 ` patchwork-bot+chrome-platform [this message]
2024-06-14 2:50 ` patchwork-bot+chrome-platform
2024-06-14 5:05 ` Dan Carpenter
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=171833343030.26166.18265568049906773511.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=ben@jubnut.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dan.carpenter@linaro.org \
--cc=groeck@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tzungbi@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox