Hi Gary,
On 11/05/2013 08:09 PM, Gary Robertson wrote:
Hello,
LNG has decided we need to stop maintaining our kernel tree config fragments separately from those in the main Linaro tree if possible. While assessing what has to be done to accomplish this, I noticed there have been no updates to the 3.10 branches for the past three months.
I also noticed that not only have several LNG developers contributed fragments to the config-core-tracking tree, but additionally there has been other work consolidating and enhancing fragments in that tree which looks at first glance as though it might be desirable for the LNG kernels.
However, I recognize that config variables within the kernel change names, values, and organizational relationships as the kernel evolves across release versions. Obviously we will need to incorporate the config fragments which the LNG developers added to the tracking tree, but some of the other changes might not apply to the 3.10 kernel cleanly.
So I am writing to as you as tree maintainers and as contributors of many of the recent changes to ask for a quick assessment and assist -
- how much of the recent cleanup and enhancement in the config-core-tracking branch which follows <commit ID # 0dee3586def91d706cef49dfbd2e20c9200df600 configs: Initial core configs> is also applicable to the 3.10 kernel? -and-
I've made a quick look through "non-LNG" commits missing from config-core-3.10 (starting from "kvm-host.conf: enable guest OS networking" by Kim Phillips), and they all look like applicable to the v3.10.
- do you plan to back-port any of this to the earlier config-core-3.10 branch?
No, we don't plan that. We didn't plan to maintain config fragments for the older kernel versions, just for the most recent one.
Personally, I wouldn't mind if someone from LNG or any other group which continues to use config-core-3.10 (LSK users?) take the ownership of config-core-3.10 branch.
Also, while we are at it: would it make sense if we make http://staging.git.linaro.org/kernel/configs.git "the primary" repository now (not waiting to the switch scheduled for December)? (currently the git.linaro.org/kernel/configs.git is the primary one, and the changes done to it are periodically copied to staging.g.l.o/kernel/configs.git). Then we could try using Gerrit (staging.review.linaro.org) to submit and review the changes to config fragments.
We would also like to understand how many of the recent updates in config-boards-tracking might be applicable to our 3.10 kernel.
Hard to say. E.g. as for the current Panda config fragments, the omap2plus.conf is tied to the particular kernel version (based on the omap2plus.defconfig for that kernel version); while panda.conf should be less sensitive to the particular kernel version.
Thanks, Andrey
Based on answers to the above we will have to determine whether we can get by safely with merging the tracking config branches, or if we will still need to cherry-pick selected commits into our LNG tree.
Any insight you might provide will be helpful and possibly will save us some time spent in trial-and-error experimentation.
Thanks
Gary Robertson