[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160413125310.GM2906@worktop>
Date: Wed, 13 Apr 2016 14:53:10 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, mingo@...nel.org,
jiangshanlai@...il.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
josh@...htriplett.org, tglx@...utronix.de, rostedt@...dmis.org,
dhowells@...hat.com, edumazet@...gle.com, dvhart@...ux.intel.com,
fweisbec@...il.com, oleg@...hat.com, bobby.prani@...il.com,
Davidlohr Bueso <dave@...olabs.net>,
Davidlohr Bueso <dbueso@...e.de>
Subject: Re: [PATCH memory-barriers.txt 7/7] Documentation,barriers: Mention
smp_cond_acquire()
On Tue, Apr 12, 2016 at 08:52:55AM -0700, Paul E. McKenney wrote:
> From: Davidlohr Bueso <dave@...olabs.net>
>
> ... do this next to smp_load_acquire when first mentioning
> ACQUIRE. While this call is briefly explained and ctrl
> dependencies are mentioned later, it does not hurt the reader.
Ha! just when I have a patch set in RFC to change the whole thing about
:-)
lkml.kernel.org/r/20160404122250.340636238@...radead.org
Powered by blists - more mailing lists