Any comments for this little change? It's passed on 0day testing. Thanks Alex
On 07/07/2017 10:52 AM, Alex Shi wrote: > We don't need to adjust prio before new pi_waiter adding. The prio > only need update after pi_waiter change or task priority change. > > Signed-off-by: Alex Shi <alex....@linaro.org> > Cc: Steven Rostedt <rost...@goodmis.org> > Cc: Sebastian Siewior <bige...@linutronix.de> > Cc: Mathieu Poirier <mathieu.poir...@linaro.org> > Cc: Juri Lelli <juri.le...@arm.com> > Cc: Thomas Gleixner <t...@linutronix.de> > To: linux-ker...@vger.kernel.org > To: Ingo Molnar <mi...@redhat.com> > To: Peter Zijlstra <pet...@infradead.org> > --- > kernel/locking/rtmutex.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c > index 28cd09e..d1fe41f 100644 > --- a/kernel/locking/rtmutex.c > +++ b/kernel/locking/rtmutex.c > @@ -963,7 +963,6 @@ static int task_blocks_on_rt_mutex(struct rt_mutex *lock, > return -EDEADLK; > > raw_spin_lock(&task->pi_lock); > - rt_mutex_adjust_prio(task); > waiter->task = task; > waiter->lock = lock; > waiter->prio = task->prio; > -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
