linux-kernel - Re: [PATCH v1] pwm: microchip-core: fix incorrect comparison with max period

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <173861015701.3409359.18144530519616995351.git-patchwork-notify@kernel.org>
Date: Mon, 03 Feb 2025 19:15:57 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Conor Dooley <conor@...nel.org>
Cc: linux-riscv@...ts.infradead.org, linux-pwm@...r.kernel.org,
 conor.dooley@...rochip.com, stable@...r.kernel.org,
 daire.mcnamara@...rochip.com, ukleinek@...nel.org, thierry.reding@...il.com,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] pwm: microchip-core: fix incorrect comparison with max
 period

Hello:

This patch was applied to riscv/linux.git (fixes)
by Uwe Kleine-König <ukleinek@...nel.org>:

On Wed, 22 Jan 2025 14:42:56 +0000 you wrote:
> From: Conor Dooley <conor.dooley@...rochip.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