[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFw94CZOLu-DF03sXV5gt+JPNegoCt2agvaTfApr+ndmpg@mail.gmail.com>
Date: Sat, 14 Apr 2012 09:38:50 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: paulmck@...ux.vnet.ibm.com
Cc: linux-kernel@...r.kernel.org, mingo@...e.hu, laijs@...fujitsu.com,
dipankar@...ibm.com, akpm@...ux-foundation.org,
mathieu.desnoyers@...icios.com, 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, fweisbec@...il.com,
patches@...aro.org
Subject: Re: [PATCH RFC 0/7] rcu: v2 Inlinable preemptible rcu_read_lock() and rcu_read_unlock()
On Sat, Apr 14, 2012 at 9:19 AM, Paul E. McKenney
<paulmck@...ux.vnet.ibm.com> wrote:
>
> This series is version two of the inlinable versions of preemptible
> RCU's __rcu_read_lock() and __rcu_read_unlock().
Btw, what is this supposed to apply on top of? It doesn't seem to
apply cleanly to either v3.3, v3.4-rc[12], or current top-of-tree.
I can make it apply by reducing the context to just one line for
patch#6, but your base seems to be odd.
Linus
--
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