[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gG0=AJk9wUqwMps2p-ypDre4fU-1L7EVCAZY+a75tTSg@mail.gmail.com>
Date: Fri, 30 Jan 2026 19:13:15 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Mark Brown <broonie@...nel.org>, Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: Amit Kucheria <amitk@...nel.org>, Thara Gopinath <thara.gopinath@...il.com>,
Zhang Rui <rui.zhang@...el.com>, Lukasz Luba <lukasz.luba@....com>, linux-arm-msm@...r.kernel.org,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
Aishwarya TCV <Aishwarya.TCV@....com>
Subject: Re: [PATCH] thermal/drivers/qcom/lmh: Remove spurious IRQF_ONESHOT
On Fri, Jan 30, 2026 at 7:09 PM Mark Brown <broonie@...nel.org> wrote:
>
> On Fri, Jan 30, 2026 at 07:06:06PM +0100, Rafael J. Wysocki wrote:
> > On Fri, Jan 30, 2026 at 5:55 PM Mark Brown <broonie@...nel.org> wrote:
>
> > > This warning is there because IRQF_ONESHOT is only meaningful when there is
> > > a threaded interrupt handler and this driver does not register one. Just
> > > remove IRQF_ONESHOT, it wasn't doing anything.
>
> > Daniel, do you want me to pick up this one? I can still push it for
> > 6.19 as a fix.
>
> FWIW the WARN_ON() is introduced in -next so won't be seen in v6.19
> (though the issue has been there since forever).
OK, so it need not go into 6.19, but it would be good to have in 6.20/7.0.
Powered by blists - more mailing lists