Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: patchwork-bot+chrome-platform@kernel.org
To: Guenter Roeck <linux@roeck-us.net>
Cc: tzungbi@kernel.org, chrome-platform@lists.linux.dev,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
	bleung@chromium.org, linux@weissschuh.net
Subject: Re: [PATCH] hwmon: (cros-ec_hwmon) Fix access to restricted __le16
Date: Fri, 07 Jun 2024 10:10:29 +0000	[thread overview]
Message-ID: <171775502930.9691.14409318862407601058.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240606180507.3332237-1-linux@roeck-us.net>

Hello:

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

On Thu,  6 Jun 2024 11:05:07 -0700 you wrote:
> 0-day complains:
> 
> drivers-hwmon-cros_ec_hwmon.c:sparse:sparse:cast-to-restricted-__le16
> 
> Fix by using a __le16 typed variable as parameter to le16_to_cpu().
> 
> Fixes: bc3e45258096 ("hwmon: add ChromeOS EC driver")
> Cc: Thomas Weißschuh <linux@weissschuh.net>
> Cc: Tzung-Bi Shih <tzungbi@kernel.org>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> 
> [...]

Here is the summary with links:
  - hwmon: (cros-ec_hwmon) Fix access to restricted __le16
    https://git.kernel.org/chrome-platform/c/c8a4bdca928d

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



  parent reply	other threads:[~2024-06-07 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 18:05 [PATCH] hwmon: (cros-ec_hwmon) Fix access to restricted __le16 Guenter Roeck
2024-06-06 19:53 ` Thomas Weißschuh
2024-06-06 20:16   ` Guenter Roeck
2024-06-06 20:48     ` Thomas Weißschuh
2024-06-06 21:15       ` Guenter Roeck
2024-06-07 10:10 ` patchwork-bot+chrome-platform [this message]
2024-06-07 10:10 ` patchwork-bot+chrome-platform

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=171775502930.9691.14409318862407601058.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+chrome-platform@kernel.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=linux@weissschuh.net \
    --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