[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200916125402.GR2674@hirez.programming.kicks-ass.net>
Date: Wed, 16 Sep 2020 14:54:02 +0200
From: peterz@...radead.org
To: Qian Cai <cai@...hat.com>
Cc: Boqun Feng <boqun.feng@...il.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
"Ahmed S. Darwish" <a.darwish@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"Sebastian A. Siewior" <bigeasy@...utronix.de>,
"Paul E. McKenney" <paulmck@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>, linux-next@...r.kernel.org,
Waiman Long <longman@...hat.com>
Subject: Re: [PATCH v2 0/5] seqlock: Introduce PREEMPT_RT support
On Wed, Sep 16, 2020 at 08:52:07AM -0400, Qian Cai wrote:
> On Tue, 2020-09-15 at 16:30 +0200, peterz@...radead.org wrote:
> > On Tue, Sep 15, 2020 at 08:48:17PM +0800, Boqun Feng wrote:
> > > I think this happened because seqcount_##lockname##_init() is defined at
> > > function rather than macro, so when the seqcount_init() gets expand in
> >
> > Bah! I hate all this :/
> >
> > I suspect the below, while more verbose than I'd like is the best
> > option.
>
> Stephen, can you add this patch for now until Peter beats you to it?
Did you verify it works? I only wrote it..
Powered by blists - more mailing lists