On 02/27/2015 08:17 PM, Juri Lelli wrote:
Hi Amit,
On 19/02/15 10:40, Amit Kucheria wrote:
Hi Juri,
Not sure what update you were waiting for, but Alex has gone ahead and split the current patch stack into stable/sched-upstream and stable/sched-core branches. So any updates from you should apply on top of the stable/sched-core branch. If you've rebased the patchset, please let Alex know in your pull request so we can replace the entire branch[1].
Thanks for the information, I've found the new branches and used them as a basis for the new backport. However, I also noticed that the wikipage is not yet updated. Can we put some information on how we intend to manage the thing there?
Regarding the EASv3 backport, I had also to backport 5 additional patches from mainline that should go on top of the upstream branch. The EASv3 backport patches apply on top of upstream (with those 5 patches). I attach an archive containing them. Is there a proper way to issue a pull request to Alex or is this way just fine? I could post them on the list as a patch series maybe.
Hi, Juri the upstream branch is ok for me. but when applying the easv6 by 'git am' basing on new upstream branch, I hit the following error: Would you like to look into this issue?
Applying: sched: Infrastructure to query if load balancing is energy-aware error: patch failed: kernel/sched/fair.c:5536 error: kernel/sched/fair.c: patch does not apply Patch failed at 0037 sched: Infrastructure to query if load balancing is energy-aware The copy of the patch that failed is found in: /home/alexs/lsk/kernel/.git/rebase-apply/patch When you have resolved this problem, run "git am --continue". If you prefer to skip this patch, run "git am --skip" instead. To restore the original branch and stop patching, run "git am --abort".