From: Thomas Gleixner <tglx@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Molnar Ingo <mingo@kernel.org>, Marc Zyngier <maz@kernel.org>,
Lukas Wunner <lukas@wunner.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Jon Hunter <jonathanh@nvidia.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH v2] genirq/chip: Change irq_chip_pm_put() return type to void
Date: Thu, 08 Jan 2026 22:40:30 +0100 [thread overview]
Message-ID: <87secfsrzl.ffs@tglx> (raw)
In-Reply-To: <5075294.31r3eYUQgx@rafael.j.wysocki>
On Thu, Jan 08 2026 at 16:05, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> The irq_chip_pm_put() return value is only used in __irq_do_set_handler()
> to trigger a WARN_ON() if it is negative, but doing so is not useful
> because irq_chip_pm_put() simply passes the pm_runtime_put() return value
> to its callers.
>
> Returning an error code from pm_runtime_put() merely means that it has
> not queued up a work item to check whether or not the device can be
> suspended and there are many perfectly valid situations in which that
> can happen, like after writing "on" to the devices' runtime PM "control"
> attribute in sysfs for one example.
>
> For this reason, modify irq_chip_pm_put() to discard the pm_runtime_put()
> return value, change its return type to void, and drop the WARN_ON()
> around the irq_chip_pm_put() invocation from __irq_do_set_handler().
> Also update the irq_chip_pm_put() kerneldoc comment to be more accurate.
>
> This will facilitate a planned change of the pm_runtime_put() return
> type to void in the future.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
>
> This patch is requisite for converting pm_runtime_put() into a void
> function.
>
> If you decide to pick it up, please let me know.
>
> Otherwise, an ACK or equivalent will be appreciated, but also the lack
> of specific criticism will be eventually regarded as consent.
>
> The v1 is here:
>
> https://lore.kernel.org/linux-pm/4723896.LvFx2qVVIh@rafael.j.wysocki/
>
> v1 -> v2:
> * Fix a typo in the new part of the irq_chip_pm_put() kerneldoc comment
> and rephrase it slightly.
Still:
Reviewed-by: Thomas Gleixner <tglx@kernel.org>
prev parent reply other threads:[~2026-01-08 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 15:05 [PATCH v2] genirq/chip: Change irq_chip_pm_put() return type to void Rafael J. Wysocki
2026-01-08 21:40 ` Thomas Gleixner [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=87secfsrzl.ffs@tglx \
--to=tglx@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=briannorris@chromium.org \
--cc=frederic@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=maz@kernel.org \
--cc=mingo@kernel.org \
--cc=rafael@kernel.org \
--cc=ulf.hansson@linaro.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