[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190219162250.GC32494@hirez.programming.kicks-ass.net>
Date: Tue, 19 Feb 2019 17:22:50 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Phil Auld <pauld@...hat.com>
Cc: mingo@...nel.org, tglx@...utronix.de, pjt@...gle.com,
tim.c.chen@...ux.intel.com, torvalds@...ux-foundation.org,
linux-kernel@...r.kernel.org, subhra.mazumdar@...cle.com,
fweisbec@...il.com, keescook@...omium.org, kerrnel@...gle.com
Subject: Re: [RFC][PATCH 03/16] sched: Wrap rq::lock access
On Tue, Feb 19, 2019 at 11:13:43AM -0500, Phil Auld wrote:
> On Mon, Feb 18, 2019 at 05:56:23PM +0100 Peter Zijlstra wrote:
> > In preparation of playing games with rq->lock, abstract the thing
> > using an accessor.
> >
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
>
> Hi Peter,
>
> Sorry... what tree are these for? They don't apply to mainline.
> Some branch on tip, I guess?
tip/master I think; any rejects should be trivial tough.
Powered by blists - more mailing lists