[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpmjNOBJ12xUY9+tXx5ezFoFqo4BU4SLK7xofMGexvGNQR7tA@mail.gmail.com>
Date: Wed, 21 Jan 2026 19:35:14 +0100
From: Marco Elver <elver@...gle.com>
To: Bart Van Assche <bvanassche@....org>
Cc: Peter Zijlstra <peterz@...radead.org>, linux-kernel@...r.kernel.org,
bigeasy@...utronix.de, mingo@...nel.org, tglx@...utronix.de, will@...nel.org,
boqun.feng@...il.com, longman@...hat.com, hch@....de, rostedt@...dmis.org,
llvm@...ts.linux.dev
Subject: Re: [RFC][PATCH 1/4] compiler-context-analysys: Add __cond_releases()
On Wed, 21 Jan 2026 at 18:55, Bart Van Assche <bvanassche@....org> wrote:
>
> On 1/21/26 3:07 AM, Peter Zijlstra wrote:
> > +#define __cond_releases(ret, x) __releases(x) __cond_acquires_impl_not_##ret(x)
>
> Since we have __cond_acquires() and __cond_acquires_shared(), how about
> also adding a __cond_releases_shared() macro?
Since I'm a fan of less code, another option is to introduce it when
needed. It's unlikely to be needed, and until then I'd prefer fewer
lines of code to be included and maintained. Up to you.
Powered by blists - more mailing lists