There are few original branches which other teams are pulling in their trees directly but they can not be cleanly updated and pulled into LSK. So I end up creating new branches for pull requests. But then some branch names are just too big to be put in single line for pull requests and hence breaking the pull requests. So I have to come up with a shorter name. To cut a long story short, I'll be using lsk-vX.YZ-android branch names for all future pull requests.
Thanks for explanations! :)
Amit, Just find some extra error which seems introduced by this new android branch, A build error on x86 with allmodconfig + CONFI_OF=n. Anyway it isn't critical. https://kernelci.org/build/lsk/kernel/lsk-v4.4-16.01-546-g02bbd06e489a/defco...
But we have 5/118 boot errors, while the last time lsk-4.4-android just has none failure. Could you like to look into them?
https://kernelci.org/boot/all/job/lsk/kernel/lsk-v4.4-16.01-546-g02bbd06e489...
For all lsk testing: https://kernelci.org/job/lsk/
Regards ALex