[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240111161915.QlfL1DLS@linutronix.de>
Date: Thu, 11 Jan 2024 17:19:15 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Paolo Abeni <pabeni@...hat.com>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Boqun Feng <boqun.feng@...il.com>,
Daniel Borkmann <daniel@...earbox.net>,
Eric Dumazet <edumazet@...gle.com>,
Frederic Weisbecker <frederic@...nel.org>,
Ingo Molnar <mingo@...hat.com>, Jakub Kicinski <kuba@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Waiman Long <longman@...hat.com>, Will Deacon <will@...nel.org>
Subject: Re: [PATCH net-next 01/24] locking/local_lock: Introduce guard
definition for local_lock.
On 2023-12-18 09:16:49 [+0100], Paolo Abeni wrote:
> > --- a/include/linux/local_lock.h
> > +++ b/include/linux/local_lock.h
> > @@ -51,4 +51,15 @@
> > #define local_unlock_irqrestore(lock, flags) \
> > __local_unlock_irqrestore(lock, flags)
> >
> > +DEFINE_LOCK_GUARD_1(local_lock, local_lock_t,
> > + local_lock(_T->lock),
> > + local_unlock(_T->lock))
> > +DEFINE_LOCK_GUARD_1(local_lock_irq, local_lock_t,
> > + local_lock_irq(_T->lock),
> > + local_unlock_irq(_T->lock))
>
> DEFINE_GUARD should fit for the 2 above, right?
Yes, that will work. Let me update it.
> Cheers,
>
> Paolo
Sebastian
Powered by blists - more mailing lists