From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, linux-pwm@vger.kernel.org,
conor.dooley@microchip.com, stable@vger.kernel.org,
daire.mcnamara@microchip.com, ukleinek@kernel.org,
thierry.reding@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] pwm: microchip-core: fix incorrect comparison with max period
Date: Mon, 03 Feb 2025 19:15:57 +0000 [thread overview]
Message-ID: <173861015701.3409359.18144530519616995351.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250122-pastor-fancied-0b993da2d2d2@spud>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Uwe Kleine-König <ukleinek@kernel.org>:
On Wed, 22 Jan 2025 14:42:56 +0000 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> In mchp_core_pwm_apply_locked(), if hw_period_steps is equal to its max,
> an error is reported and .apply fails. The max value is actually a
> permitted value however, and so this check can fail where multiple
> channels are enabled.
>
> [...]
Here is the summary with links:
- [v1] pwm: microchip-core: fix incorrect comparison with max period
https://git.kernel.org/riscv/c/752b6e3af374
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-03 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 14:42 [PATCH v1] pwm: microchip-core: fix incorrect comparison with max period Conor Dooley
2025-01-23 15:15 ` Uwe Kleine-König
2025-02-03 19:15 ` patchwork-bot+linux-riscv [this message]
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=173861015701.3409359.18144530519616995351.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=ukleinek@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