From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?q?Uwe_Kleine-K=C3=B6nig_=3Cu=2Ekleine-koenig=40baylibre=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-riscv@lists.infradead.org, linux-pwm@vger.kernel.org,
claudiu.beznea@tuxon.dev, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com,
linux-arm-kernel@lists.infradead.org, vz@mleia.com,
conor.dooley@microchip.com, daire.mcnamara@microchip.com,
wens@csie.org, jernej.skrabec@gmail.com, samuel@sholland.org,
linux-sunxi@lists.linux.dev
Subject: Re: [PATCH 0/8] pwm: Drop local locking in several drivers
Date: Sun, 10 Aug 2025 21:12:26 +0000 [thread overview]
Message-ID: <175486034649.1221929.797683482600200009.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1750788649.git.u.kleine-koenig@baylibre.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Uwe Kleine-König <ukleinek@kernel.org>:
On Tue, 24 Jun 2025 20:15:36 +0200 you wrote:
> Hello,
>
> some time ago the pwm core implemented additional locking to protect
> lowlevel driver callbacks against driver removal. A side effect is that
> .apply() and .get_state() are serialized. This allows to drop some
> locking that is now superfluous due to the core's locking.
>
> [...]
Here is the summary with links:
- [5/8] pwm: microchip-core: Drop driver local locking
https://git.kernel.org/riscv/c/9470e7d11fe2
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-08-10 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 18:15 [PATCH 0/8] pwm: Drop local locking in several drivers Uwe Kleine-König
2025-06-24 18:15 ` [PATCH 7/8] pwm: sun4i: Drop driver local locking Uwe Kleine-König
2025-07-01 7:57 ` [PATCH 0/8] pwm: Drop local locking in several drivers Uwe Kleine-König
2025-08-10 21:12 ` 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=175486034649.1221929.797683482600200009.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc==?utf-8?q?Uwe_Kleine-K=C3=B6nig_=3Cu=2Ekleine-koenig=40baylibre=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=nicolas.ferre@microchip.com \
--cc=samuel@sholland.org \
--cc=vz@mleia.com \
--cc=wens@csie.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