Hi,
I had a good discussion with the validation team and they are going to try to have some automated defconfig building working by the end of the week. What they need from us is :
- What defconfigs do we want them to build? Either defconfigs that are in the kernel tree or that are out of tree. My thought is one per board that we care about, but I'm not sure if all the boards have upstream defconfigs.
- What trees to test? I'm thinking linus HEAD and also the arm-soc tree's -next branch.
~Deepak
On Monday 01 August 2011, Deepak Saxena wrote:
I had a good discussion with the validation team and they are going to try to have some automated defconfig building working by the end of the week. What they need from us is :
- What defconfigs do we want them to build? Either defconfigs that are in the kernel tree or that are out of tree. My thought is one per board that we care about, but I'm not sure if all the boards have upstream defconfigs.
If we care about the boards enough, they should really have defconfigs upstream. We can skip the ones that don't for now, and we can also put the defconfig files into the arm-soc tree.
- What trees to test? I'm thinking linus HEAD and also the arm-soc tree's -next branch.
Yes, at least these two. We could also consider the actual linux-next tree, as well as the linaro kernel tree. The linux-next tree would likely break more often, but that would give us very valuable feedback.
Arnd
On Mon, 1 Aug 2011, Deepak Saxena wrote:
Hi,
I had a good discussion with the validation team and they are going to try to have some automated defconfig building working by the end of the week. What they need from us is :
What defconfigs do we want them to build? Either defconfigs that are in the kernel tree or that are out of tree. My thought is one per board that we care about, but I'm not sure if all the boards have upstream defconfigs.
What trees to test? I'm thinking linus HEAD and also the arm-soc tree's -next branch.
Are they going to do boot tests as well? If so, having a config that simply compiles everything in the kernel with no modules is certainly going to make their job easier (no initrd creation, no packaging, no native compilation necessary, etc). Most problems are going to be failing builds or non booting kernels. Knowing about those classes of problems daily or more would be highly valuable.
Testing the full food chain result is of course important as well, but problems outside the above categories are less frequent.
Nicolas
linaro-kernel@lists.linaro.org
-
Arnd Bergmann -
Deepak Saxena -
Nicolas Pitre