Re: [PATCH v2 07/12] locking: Switch to _irq_{disable,enable}() variants in cleanup guards
Boqun Feng <[email protected]> Thu, 28 May 2026 07:31:52 -0700
| Newsgroups | org.kernel.vger.linux-openrisc,org.kernel.vger.bpf,org.kernel.vger.linux-arch,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest,org.kernel.vger.linux-s390,org.kernel.vger.rust-for-linux |
|---|---|
| Message-ID | <[email protected]> |
On Thu, May 28, 2026 at 12:45:29PM +0200, Peter Zijlstra wrote: > On Tue, May 26, 2026 at 08:21:43AM -0700, Boqun Feng wrote: > > From: Boqun Feng <[email protected]> > > > > The semantics of various irq disabling guards match what > > *_irq_{disable,enable}() provide, i.e. the interrupt disabling is > > properly nested, therefore it's OK to switch to use > > *_irq_{disable,enable}() primitives. > > > > Signed-off-by: Boqun Feng <[email protected]> > > Signed-off-by: Boqun Feng <[email protected]> > > You really need them both? ;-) Nah, I will clean this up ;-) Regards, Boqun