Amit Pundir amit.pundir@linaro.org writes:
On 17 June 2015 at 04:19, Kevin Hilman khilman@linaro.org wrote:
Kevin Hilman khilman@linaro.org writes:
Amit Pundir amit.pundir@linaro.org writes:
Hi Kevin, Alex,
Please consider following linaro-android pull request for "linux-linaro-lsk-v3.18-android" branch.
Regards, Amit Pundir
The following changes since commit 256c032b3f7d6491ae4ca424510ca5829abe499c:
export tcp_nuke_addr to build ipv6 as module (2015-05-12 21:32:27 +0530)
are available in the git repository at:
git://android.git.linaro.org/kernel/linaro-android.git linaro-android-3.18-lsk
for you to fetch changes up to 028d5c1bb15977715f4c5d8c7827deec05a3fb59:
Merge branch 'android-3.18' of https://android.googlesource.com/kernel/common (2015-06-04 13:02:57 +0530)
Pulled, thanks.
I pulled this into the lsk-v3.18-android-test branch to give it a spin through kernelci.org[1] and noticed it had a some build errors for arm32 and arm64 with the android defconfig fragments[1] (do you guys test these?)
These errors look really interesting. I don't really use config fragments but I was pretty sure that I had all the android configs covered. I build and boot test lsk-3.18-android for Qemu (or IFC6410 sometimes) and build test for Hikey. Can you please share the defconfigs other than android's which you use in this CI build? I'd be really interested in looking at this failure and fix my defconfigs accordingly.
All I do is use ./scripts/kconfig/merge_config.sh to combine the base config with the fragments in android/configs/*.cfg e.g.
export ARCH=arm64 make defconfig ./scripts/kconfig/merge_config.sh .config android/configs/android-base.cfg android/configs/android-recommended.cfg make
Note that the current lsk-v3.18-android-test branch includes my proposed AOSP fixes, which avoid the problem, but if you want to test if you can reproduce the build failures, you can try at commit ad689af687fa7ee83fe560744f700393fd879015
In both cases, these are fixed by the patch I have pending in the android-review system[2], but I haven't got any feedback on my pending patches there. I haven't done AOSP submissions before, any idea how these might eventually get merged?
What I have learned so far is that it is really hard to get their attention on a non-production kernel (e.g. android-3.18) fixes. So usually I try to reproduce the failure and submit my fixes on a production kernel (android-3.10 or 3.14) if possible and if they accept those fixes then they cherry-pick it on 3.18 as well. Well most of the time otherwise I submit another change with the cherry-picked patch on android-3.18. In short if the fix is specific to android-3.18 then it is really hard to get their attention on gerrit.
Ugh, ok. Thanks for the tip.
Kevin