From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: netdev@vger.kernel.org, linux-mips@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next v2] declance: Remove IRQF_ONESHOT
Date: Tue, 5 May 2026 17:24:50 +0200 [thread overview]
Message-ID: <20260505152450.1KYVS2pr@linutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2605051410280.46195@angie.orcam.me.uk>
On 2026-05-05 15:00:56 [+0100], Maciej W. Rozycki wrote:
>
> Ah, I missed that IRQF_ONESHOT bit in irq_setup_forced_threading(). So
> it seems like we're good. I'll proceed with the original change then to
> just amend IOASIC DMA IRQ documentation. Thank you for patience again.
No worries, you are welcome.
I'm not if sure if you may need to change the primary handler if the
interrupt flow is EOI and cascading based on what you wrote. If you have
access to the HW then you it should be easy to test given the
`threadirqs' argument should expose problems.
> Maciej
Sebastian
next prev parent reply other threads:[~2026-05-05 15:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 13:53 [PATCH net-next v2] declance: Remove IRQF_ONESHOT Sebastian Andrzej Siewior
2026-01-27 15:46 ` Maciej W. Rozycki
2026-01-27 16:54 ` Sebastian Andrzej Siewior
2026-01-27 18:35 ` Maciej W. Rozycki
2026-03-29 20:27 ` Maciej W. Rozycki
2026-05-04 22:35 ` Maciej W. Rozycki
2026-05-05 7:29 ` Sebastian Andrzej Siewior
2026-05-05 12:02 ` Maciej W. Rozycki
2026-05-05 12:32 ` Sebastian Andrzej Siewior
2026-05-05 14:00 ` Maciej W. Rozycki
2026-05-05 15:24 ` Sebastian Andrzej Siewior [this message]
2026-01-29 3:50 ` patchwork-bot+netdevbpf
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=20260505152450.1KYVS2pr@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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