linux-kernel - [PATCH v1 00/23] PM: runtime: Convert pm_runtime

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-next>] [day] [month] [year] [list]

Message-ID: <6245770.lOV4Wx5bFT@rafael.j.wysocki>
Date: Mon, 22 Dec 2025 20:48:11 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Linux PM <linux-pm@...r.kernel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Ulf Hansson <ulf.hansson@...aro.org>,
 Brian Norris <briannorris@...omium.org>
Subject:
 [PATCH v1 00/23] PM: runtime: Convert pm_runtime_put() to a void function

Hi All,

This is something I have had on my todo list for some time, but it is
kind of tricky because the return value of pm_runtime_put() is used in
some places all over the tree.

Nevertheless, I think that it is worth doing because the majority of
users of the pm_runtime_put() return value are at least somewhat
questionable (in fact, IMV the only legitimate use of it is in the
USB core where it is included in a debug message).

This series goes through all of the users of the pm_runtime_put()
return value an makes them discard it.  Patches [1-22/23] are
independent of each other and they can be processed separately,
but the last patch (obviously) depends on all of them.  Each of
them will be sent to the respective maintainers and it doesn't
matter too much how they are handled, so long as they end up in
the mainline eventually.

Thanks!