Re: [PATCH 0/3] some scheduler code movements

2017-06-22 Thread Nicolas Pitre
On Thu, 22 Jun 2017, Ingo Molnar wrote: > * Nicolas Pitre wrote: > > > That's against my copy of tip/sched/core as of yesterday: > > > > commit f11cc0760b8397e0d230122606421b6a96e9f869 > > Author: Davidlohr Bueso > > AuthorDate: Wed Jun 14

Re: [PATCH 0/3] some scheduler code movements

2017-06-22 Thread Nicolas Pitre
On Thu, 22 Jun 2017, Ingo Molnar wrote: > * Nicolas Pitre wrote: > > > That's against my copy of tip/sched/core as of yesterday: > > > > commit f11cc0760b8397e0d230122606421b6a96e9f869 > > Author: Davidlohr Bueso > > AuthorDate: Wed Jun 14 19:37:30 2017 -0700 > > Commit: Ingo Molnar

Re: [PATCH 0/3] some scheduler code movements

2017-06-22 Thread Ingo Molnar
* Nicolas Pitre wrote: > On Thu, 22 Jun 2017, Ingo Molnar wrote: > > > > > * Nicolas Pitre wrote: > > > > > On Wed, 21 Jun 2017, Ingo Molnar wrote: > > > > > > > I've applied the first patch to the scheduler tree yesterday, but the > > >

Re: [PATCH 0/3] some scheduler code movements

2017-06-22 Thread Ingo Molnar
* Nicolas Pitre wrote: > On Thu, 22 Jun 2017, Ingo Molnar wrote: > > > > > * Nicolas Pitre wrote: > > > > > On Wed, 21 Jun 2017, Ingo Molnar wrote: > > > > > > > I've applied the first patch to the scheduler tree yesterday, but the > > > > other > > > > changes unfortunately conflicted

Re: [PATCH 0/3] some scheduler code movements

2017-06-22 Thread Nicolas Pitre
On Thu, 22 Jun 2017, Ingo Molnar wrote: > > * Nicolas Pitre wrote: > > > On Wed, 21 Jun 2017, Ingo Molnar wrote: > > > > > I've applied the first patch to the scheduler tree yesterday, but the > > > other > > > changes unfortunately conflicted with other pending

Re: [PATCH 0/3] some scheduler code movements

2017-06-22 Thread Nicolas Pitre
On Thu, 22 Jun 2017, Ingo Molnar wrote: > > * Nicolas Pitre wrote: > > > On Wed, 21 Jun 2017, Ingo Molnar wrote: > > > > > I've applied the first patch to the scheduler tree yesterday, but the > > > other > > > changes unfortunately conflicted with other pending scheduler work - could > > >

Re: [PATCH 0/3] some scheduler code movements

2017-06-22 Thread Ingo Molnar
* Nicolas Pitre wrote: > On Wed, 21 Jun 2017, Ingo Molnar wrote: > > > I've applied the first patch to the scheduler tree yesterday, but the other > > changes unfortunately conflicted with other pending scheduler work - could > > you please re-post the other 3 patches

Re: [PATCH 0/3] some scheduler code movements

2017-06-22 Thread Ingo Molnar
* Nicolas Pitre wrote: > On Wed, 21 Jun 2017, Ingo Molnar wrote: > > > I've applied the first patch to the scheduler tree yesterday, but the other > > changes unfortunately conflicted with other pending scheduler work - could > > you please re-post the other 3 patches on top of tip:sched/core?

[PATCH 0/3] some scheduler code movements

2017-06-21 Thread Nicolas Pitre
On Wed, 21 Jun 2017, Ingo Molnar wrote: > I've applied the first patch to the scheduler tree yesterday, but the other > changes unfortunately conflicted with other pending scheduler work - could > you please re-post the other 3 patches on top of tip:sched/core? Sure, here they are.

[PATCH 0/3] some scheduler code movements

2017-06-21 Thread Nicolas Pitre
On Wed, 21 Jun 2017, Ingo Molnar wrote: > I've applied the first patch to the scheduler tree yesterday, but the other > changes unfortunately conflicted with other pending scheduler work - could > you please re-post the other 3 patches on top of tip:sched/core? Sure, here they are.