[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170609133331.484953e8@gandalf.local.home>
Date: Fri, 9 Jun 2017 13:33:31 -0400
From: Steven Rostedt <rostedt@...dmis.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, peterz@...radead.org,
dhowells@...hat.com, edumazet@...gle.com, fweisbec@...il.com,
oleg@...hat.com, bobby.prani@...il.com
Subject: Re: [PATCH tip/core/rcu 0/88] Commits for 4.13
On Fri, 9 Jun 2017 10:20:38 -0700
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:
> But enough fantasizing about possible futures. Any thoughts on what
> could be done to help with this situation in the here and now?
Unfortunately no, as I don't have enough info to understand all the
interconnections between the patches to have a better idea on how to
break them apart.
But I will say, I've actually written code that would later be removed,
just to keep things better apart and bisectable.
-- Steve
Powered by blists - more mailing lists