From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Cc: hansg@kernel.org, "Kurmi,
Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
"Saarinen, Jani" <jani.saarinen@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
sfr@canb.auug.org.au, ilpo.jarvinen@linux.intel.com,
regressions@leemhuis.info
Subject: Re: REGRESSION on linux-next (next-20260115)
Date: Wed, 21 Jan 2026 08:53:48 +0100 [thread overview]
Message-ID: <20260121075348.5MyqcHFB@linutronix.de> (raw)
In-Reply-To: <555f1c56-0f74-41bf-8bd2-6217e0aab0c6@intel.com>
On 2026-01-21 12:42:16 [+0530], Borah, Chaitanya Kumar wrote:
> commit aef30c8d569c0f31715447525640044c74feb26f
> Author: Sebastian Andrzej Siewior bigeasy@linutronix.de
> Date: Mon Jan 12 14:40:13 2026 +0100
>
>
> genirq: Warn about using IRQF_ONESHOT without a threaded handler
> `````````````````````````````````````````````````````````````````````````````````````````````````````````
>
> Looking at the irq register code in int0002_vgpio.c, it seems the warning
> comes from
>
> ret = devm_request_irq(dev, irq, int0002_irq,
> IRQF_ONESHOT | IRQF_SHARED, "INT0002", chip);
>
> Looking at the history, this flag was added by the Commit 8f812373d195
> ("platform/x86: intel: int0002_vgpio: Pass IRQF_ONESHOT to request_irq()")
> to resolve another issue.
>
> Any proposals for solving the WARN_ON?
Do you have the ACPI interrupt also on the same interrupt on the board
in question?
Sebastian
next prev parent reply other threads:[~2026-01-21 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 7:12 REGRESSION on linux-next (next-20260115) Borah, Chaitanya Kumar
2026-01-21 7:53 ` Sebastian Andrzej Siewior [this message]
2026-01-21 8:29 ` Borah, Chaitanya Kumar
2026-01-21 9:01 ` Sebastian Andrzej Siewior
2026-01-21 10:20 ` Hans de Goede
2026-01-21 10:39 ` Sebastian Andrzej Siewior
2026-01-21 11:13 ` Hans de Goede
2026-01-21 12:13 ` Borah, Chaitanya Kumar
2026-01-21 13:19 ` Sebastian Andrzej Siewior
2026-01-21 9:06 ` ✗ CI.checkpatch: warning for " Patchwork
2026-01-21 9:08 ` ✓ CI.KUnit: success " Patchwork
2026-01-21 9:24 ` ✗ CI.checksparse: warning " Patchwork
2026-01-21 9:45 ` ✓ Xe.CI.BAT: success " Patchwork
2026-01-21 13:40 ` ✓ Xe.CI.Full: " Patchwork
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=20260121075348.5MyqcHFB@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=chaitanya.kumar.borah@intel.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=regressions@leemhuis.info \
--cc=sfr@canb.auug.org.au \
--cc=suresh.kumar.kurmi@intel.com \
/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