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.
Thanks a lot.
Best,
- Juri
Regards, Amit [1] Since we don't _yet_ have the complex interplay between features, we decided at Connect to lower the barrier for new features until we have a full validation cycle working and putting out reports. By then we'll need to agree on the acceptance criteria for letting in new features.
On Wed, Feb 18, 2015 at 8:05 PM, Juri Lelli juri.lelli@arm.com wrote:
Hi Amit,
since I've got a backport of EASv3 and I'd like to share this with all, can you please give me an update about the EAS backport tree maintenance bits we agreed upon.
Thanks a lot,
- Juri