From: patchwork-bot+linux-riscv@kernel.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-rt-devel@lists.linux.dev, tglx@kernel.org,
troy.mitchell@linux.spacemit.com, andi.shyti@kernel.org,
dlan@gentoo.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH 11/21] i2c: spacemit: Remove IRQF_ONESHOT
Date: Mon, 26 Jan 2026 04:21:46 +0000 [thread overview]
Message-ID: <176940130684.4057692.5555017535441416202.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260123113708.416727-12-bigeasy@linutronix.de>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Andi Shyti <andi.shyti@kernel.org>:
On Fri, 23 Jan 2026 12:36:57 +0100 you wrote:
> Passing IRQF_ONESHOT ensures that the interrupt source is masked until
> the secondary (threaded) handler is done. If only a primary handler is
> used then the flag makes no sense because the interrupt can not fire
> (again) while its handler is running.
> The flag also disallows force-threading of the primary handler and the
> irq-core will warn about this.
>
> [...]
Here is the summary with links:
- [11/21] i2c: spacemit: Remove IRQF_ONESHOT
https://git.kernel.org/riscv/c/e351836a54e3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-26 4:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260123113708.416727-1-bigeasy@linutronix.de>
2026-01-23 11:36 ` [PATCH 11/21] i2c: spacemit: Remove IRQF_ONESHOT Sebastian Andrzej Siewior
2026-01-23 20:53 ` Yixun Lan
2026-01-26 4:21 ` patchwork-bot+linux-riscv [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=176940130684.4057692.5555017535441416202.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=dlan@gentoo.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=tglx@kernel.org \
--cc=troy.mitchell@linux.spacemit.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