[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53BBB11F.5000508@cn.fujitsu.com>
Date: Tue, 8 Jul 2014 16:51:43 +0800
From: Lai Jiangshan <laijs@...fujitsu.com>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
CC: Josh Triplett <josh@...htriplett.org>,
<linux-kernel@...r.kernel.org>, <mingo@...nel.org>,
<dipankar@...ibm.com>, <akpm@...ux-foundation.org>,
<mathieu.desnoyers@...icios.com>, <niv@...ibm.com>,
<tglx@...utronix.de>, <peterz@...radead.org>,
<rostedt@...dmis.org>, <dhowells@...hat.com>,
<edumazet@...gle.com>, <dvhart@...ux.intel.com>,
<fweisbec@...il.com>, <oleg@...hat.com>, <sbw@....edu>
Subject: Re: [PATCH tip/core/rcu 0/4] Documentation changes for 3.17
On 07/08/2014 08:14 AM, Josh Triplett wrote:
> On Mon, Jul 07, 2014 at 03:23:45PM -0700, Paul E. McKenney wrote:
>> Hello!
>>
>> This series provides a few documentation updates:
>>
>> 1. Clarify that if there is nothing awakened, then there is no
>> memory barrier.
>>
>> 2. Fix broken RTFP URL, courtesy of Pranith Kumar.
>>
>> 3. Add acquire/release barrier to memory-barrier pairing rules.
>>
>> 4. Add pointer to percpu-ref in rcuref.txt documentation.
>
> For all four:
>
> Reviewed-by: Josh Triplett <josh@...htriplett.org>
> .
>
For patch 1 ("documentation: Clarify wake-up/memory-barrier relationship")
and patch 4 ("documentation: Add pointer to percpu-ref for RCU and refcount")
Reviewed-by: Lai Jiangshan <laijs@...fujitsu.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists