[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D8ABE6C.7000105@cn.fujitsu.com>
Date: Thu, 24 Mar 2011 11:45:48 +0800
From: Lai Jiangshan <laijs@...fujitsu.com>
To: paulmck@...ux.vnet.ibm.com
CC: linux-kernel@...r.kernel.org, mingo@...e.hu, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...ymtl.ca,
josh@...htriplett.org, niv@...ibm.com, tglx@...utronix.de,
peterz@...radead.org, rostedt@...dmis.org, Valdis.Kletnieks@...edu,
dhowells@...hat.com, eric.dumazet@...il.com, darren@...art.com
Subject: Re: [PATCH RFC tip/core/rcu 01/11] rcu: call __rcu_read_unlock()
in exit_rcu for tiny RCU
On 02/26/2011 03:40 AM, Paul E. McKenney wrote:
> On Fri, Feb 25, 2011 at 04:29:46PM +0800, Lai Jiangshan wrote:
>> On 02/23/2011 09:39 AM, Paul E. McKenney wrote:
>>>
>>> diff --git a/kernel/rcutiny_plugin.h b/kernel/rcutiny_plugin.h
>>> index 015abae..3cb8e36 100644
>>> --- a/kernel/rcutiny_plugin.h
>>> +++ b/kernel/rcutiny_plugin.h
>>
>> My original patch was just for tree RCU. It is not merged.
>> I forgot the tiny RCU case then, this change is needed for tree & tiny RCU.
>
> Good catch, I have applied the TREE_RCU patch. I intend to submit
> both for the next merge window.
>
Hi, Paul
It is still not merged, and it is not in your git tree.
I'm writing some patches, to avoid conflict with your code,
which branch I should based on?
Is origin/rcu/next OK?
Thanks,
Lai
--
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