linux-pwm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+chrome-platform@kernel.org
To: =?utf-8?q?Uwe_Kleine-K=C3=B6nig_=3Cu=2Ekleine-koenig=40pengutronix=2Ede=3E?=@ci.codeaurora.org
Cc: thierry.reding@gmail.com, kamatam@amazon.com,
	xuejiancheng@hisilicon.com, yuanjian12@hisilicon.com,
	robh@kernel.org, bleung@chromium.org, orsonzhai@gmail.com,
	baolin.wang@linux.alibaba.com, zhang.lyra@gmail.com,
	linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
	groeck@chromium.org, chrome-platform@lists.linux.dev,
	kernel@pengutronix.de
Subject: Re: [PATCH 0/4] pwm: Ensure .polarity is set in .get_state()
Date: Mon, 08 May 2023 03:45:14 +0000	[thread overview]
Message-ID: <168351751434.5651.3110198829137956181.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230228135508.1798428-1-u.kleine-koenig@pengutronix.de>

Hello:

This patch was applied to chrome-platform/linux.git (for-kernelci)
by Thierry Reding <thierry.reding@gmail.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



  parent reply	other threads:[~2023-05-08  3:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 13:55 [PATCH 0/4] pwm: Ensure .polarity is set in .get_state() Uwe Kleine-König
2023-02-28 13:55 ` [PATCH 1/4] pwm: hibvt: Explicitly set .polarity " Uwe Kleine-König
2023-03-10 18:59   ` Uwe Kleine-König
2023-02-28 13:55 ` [PATCH 2/4] pwm: cros-ec: " Uwe Kleine-König
2023-02-28 16:19   ` Guenter Roeck
2023-03-10 18:50   ` Uwe Kleine-König
2023-02-28 13:55 ` [PATCH 3/4] pwm: iqs620a: " Uwe Kleine-König
2023-03-10 18:48   ` Uwe Kleine-König
2023-03-10 23:29     ` Jeff LaBundy
2023-02-28 13:55 ` [PATCH 4/4] pwm: sprd: " Uwe Kleine-König
2023-03-10 18:43   ` Uwe Kleine-König
2023-05-08  3:45 ` patchwork-bot+chrome-platform [this message]
2023-05-08  3:56 ` [PATCH 0/4] pwm: Ensure .polarity is set " 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=168351751434.5651.3110198829137956181.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+chrome-platform@kernel.org \
    --cc==?utf-8?q?Uwe_Kleine-K=C3=B6nig_=3Cu=2Ekleine-koenig=40pengutronix=2Ede=3E?=@ci.codeaurora.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=groeck@chromium.org \
    --cc=kamatam@amazon.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=orsonzhai@gmail.com \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=xuejiancheng@hisilicon.com \
    --cc=yuanjian12@hisilicon.com \
    --cc=zhang.lyra@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).