[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180412082010.3f088370@gandalf.local.home>
Date: Thu, 12 Apr 2018 08:20:10 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Li Bin <huawei.libin@...wei.com>, mingo@...hat.com,
linux-kernel@...r.kernel.org, guohanjun@...wei.com
Subject: Re: [PATCH 0/2] sched: pick and check task if double_lock_balance()
unlock the rq
On Thu, 12 Apr 2018 14:11:45 +0200
Peter Zijlstra <peterz@...radead.org> wrote:
> On Thu, Apr 12, 2018 at 06:58:53PM +0800, Li Bin wrote:
> > Li Bin (1):
> > sched/deadline.c: pick and check task if double_lock_balance() unlock
> > the rq
> >
> > Zhou Chengming (1):
> > sched/rt.c: pick and check task if double_lock_balance() unlock the
> > rq
> >
>
> Much thanks!
>
> Acked-by: Peter Zijlstra (Intel) <peterz@...radead.org>
>
> Ingo, please apply.
You can add my:
Reviewed-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
but I would still like to see the declaration of next_task before the
comment, just for style concerns.
-- Steve
Powered by blists - more mailing lists