[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168351816176.5651.17672713691449446038.git-patchwork-notify@kernel.org>
Date: Mon, 08 May 2023 03:56:01 +0000
From: patchwork-bot+chrome-platform@...nel.org
To: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>@ci.codeaurora.org
Cc: thierry.reding@...il.com, kamatam@...zon.com,
xuejiancheng@...ilicon.com, yuanjian12@...ilicon.com,
robh@...nel.org, bleung@...omium.org, orsonzhai@...il.com,
baolin.wang@...ux.alibaba.com, zhang.lyra@...il.com,
linux-pwm@...r.kernel.org, linux-kernel@...r.kernel.org,
groeck@...omium.org, chrome-platform@...ts.linux.dev,
kernel@...gutronix.de
Subject: Re: [PATCH 0/4] pwm: Ensure .polarity is set in .get_state()
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Thierry Reding <thierry.reding@...il.com>:
On Tue, 28 Feb 2023 14:55:04 +0100 you wrote:
> Hello,
>
> in the context of the discussion with Munehisa Kamata about the meson driver
> not setting .polarity in .get_state() I checked the other drivers for the same
> issue. The identified drivers are fixed here. For three of them
> zero-initializing *state would be good enough, still I think setting the
> polarity explicitly is a good idea. For the hibvt driver (that supports
> both polarities) the change is a real improvement.
>
> [...]
Here is the summary with links:
- [2/4] pwm: cros-ec: Explicitly set .polarity in .get_state()
https://git.kernel.org/chrome-platform/c/30006b77c7e1
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