On Mon, 2012-11-19 at 22:24 +0400, Andrey Konovalov wrote: > On 11/19/2012 10:17 PM, Jon Medhurst (Tixy) wrote: > > On Mon, 2012-11-19 at 21:14 +0400, Andrey Konovalov wrote: > >> Viresh, > >> > >> I won't pull the big-LITTLE-MP-master-v12 into the > >> linux-linaro-core-tracking tree today due to the issues found by Tixy. > >> > >> Tomorrow evening I am going to pull this topic anyway - whether these > >> issues are resolved, or not. If the build error is not fixed by Thursday > >> morning UTC, I'll move llct back to v11. Would it work for the Landing > >> Teams? Tixy? > > > > The timescales seem a bit wrong for that, working backwards... > > That's correct.. > > > - The monthly release is made from linux-linaro's state at end of > > Thursday. > > > > - You need to merge Landing Team's topics in before then. > > > > - Landing Teams need to prepare their topics based on a given llct. > > > > - To prepare their topics, Landing Teams need to be able to compile > > their kernels. > > > > So I would say that LT's need a final working llct tomorrow really. I > > could manage OK getting this on Wednesday, don't know about other teams. > > > > That's would then mean the monthly release candidate build comes from a > > tree who's contents have never been built together before that day, so > > it's trusting to luck somewhat. > > > > Last month llct was created by the Monday morning so LT's could base > > their branches on that and have them merged into linux-linaro by the end > > of Tuesday. We then had two days to fix problems before Thursday's code > > cutoff. > > I'll push updated llct tree with v11 big-LITTLE-MP topic tonight. > If there is the build error fix by tomorrow, I can push one more llct > update using the updated master v12 version tomorrow.
That's sounds like a sensible plan :-) > Is the boot delay > issue a show-stopper? It's not a show-stopper. It only manifests with a new config option in the big-LITTPLE-MP config, so doesn't impact any board other than vexpress and if required I could override it in my tree or we could add a simple patch to linux-linaro later. Someone else can't reproduce the problem so the slowness could be user error on my part. (The build failure problem is definitely real though :-) -- Tixy _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
