On 07/13/2017 12:35 AM, Peter Zijlstra wrote:
> On Wed, Jul 12, 2017 at 10:14:49AM -0400, Steven Rostedt wrote:
>> On Tue, 11 Jul 2017 22:39:24 +0800
>> Alex Shi wrote:
>>
>>> Any comments for this little change? It's passed on 0day testing.
>>
>> I think the problem was that this was a third pa
On 07/12/2017 10:14 PM, Steven Rostedt wrote:
> On Tue, 11 Jul 2017 22:39:24 +0800
> Alex Shi wrote:
>
>> Any comments for this little change? It's passed on 0day testing.
>
> I think the problem was that this was a third patch after two
> documentation patches. Where, people put documentation
On Wed, Jul 12, 2017 at 10:14:49AM -0400, Steven Rostedt wrote:
> On Tue, 11 Jul 2017 22:39:24 +0800
> Alex Shi wrote:
>
> > Any comments for this little change? It's passed on 0day testing.
>
> I think the problem was that this was a third patch after two
> documentation patches. Where, people
On Tue, 11 Jul 2017 22:39:24 +0800
Alex Shi wrote:
> Any comments for this little change? It's passed on 0day testing.
I think the problem was that this was a third patch after two
documentation patches. Where, people put documentation review at the
bottom of their priority list.
This should ha
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
> Cc: Steven
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
Cc: Steven Rostedt
Cc: Sebastian Siewior
Cc: Mathieu Poirier
Cc: Juri Lelli
Cc: Thomas Gleixner
To: linux-ker...@vger.kernel.org
To: Ing
