Hi Andrey
Now I'm providing a single LT topic based off linux-linaro-core-tracking (llct), and you said that you need everyone to base off the same version of llct, don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Hi Tixy
On 10/04/2012 12:55 PM, Jon Medhurst (Tixy) wrote:
Hi Andrey
Now I'm providing a single LT topic based off linux-linaro-core-tracking (llct), and you said that you need everyone to base off the same version of llct,
Yes, this is currently the case.
don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number) * till the end of this week please use llct-20121004.0 as the base for the linux-linaro (ll) topics * October 9: ll rebuild based on llct-20121005.<N> * October 16: ll rebuild based on llct-20121012.<N> * October 23: ll rebuild based on llct-20121019.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
ll and llct could be updated between these dates as well, but without changes in the "normal" ll topics - just my "last-time-fixes" pseudo topics could change.
Also I believe that the ll topics could actually based on *any* recent enough llct version. But I want to double check the pro's and contra's before making this statement official.
What concerns me now are the ll topics based on ll itself (just one real topic atm: ste-lt-next). Would it be a problem for any of the topic maintainers if I request all the ll topics to be based on llct, on another ll topic (I must be told about that), even on vM.N-rcX kernel.org tag if this is good for the topic maintainer, but not on ll itself?
Thanks, Andrey
PS The multiplatform topic is removed from llct starting from llct-20120924.0
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number)
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>
- October 23: ll rebuild based on llct-20121019.<N>, ll code freeze (no
massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Also, I assume we're not going to try to move to Linux 3.7 this month?
On 10/05/2012 01:42 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number)
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>
- October 23: ll rebuild based on llct-20121019.<N>, ll code freeze (no
massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Also, I assume we're not going to try to move to Linux 3.7 this month?
Samsung LT release would be based on Linux-v3.6 final release, no plans to move to 3.7 during 12.10.
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number)
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>
- October 23: ll rebuild based on llct-20121019.<N>, ll code freeze (no
massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Oops.. Your are right. Why don't we have the Thursday, October 32 this year?
So the correct plan is the following: * till the end of this week please use llct-20121004.0 as the base for the linux-linaro (ll) topics * October 9: ll rebuild based on llct-20121005.<N> * October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
Also, I assume we're not going to try to move to Linux 3.7 this month?
That's correct. We didn't have the kernel.org release based (vs -rc based) ll release for quite a while. And the plan is to stick to v3.6 for 12.10 release unless someone needs to move to v3.7-rc* by all means this cycle. After October 19 the llct tree will move to v3.7-rc*, but the ll tree will be frozen till the 12.10 is out.
Thanks, Andrey
On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number)
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>
- October 23: ll rebuild based on llct-20121019.<N>, ll code freeze (no
massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Oops.. Your are right. Why don't we have the Thursday, October 32 this year?
So the correct plan is the following:
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
Also, I assume we're not going to try to move to Linux 3.7 this month?
That's correct. We didn't have the kernel.org release based (vs -rc based) ll release for quite a while. And the plan is to stick to v3.6 for 12.10 release unless someone needs to move to v3.7-rc* by all means this cycle. After October 19 the llct tree will move to v3.7-rc*, but the ll tree will be frozen till the 12.10 is out.
That all sounds reasonable to me.
Greetings,
Minor change to the plan: * The current llct is *llct-20121006.0* * October 9: ll rebuild based on llct-20121006.0 * October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
Thanks, Andrey
On 10/05/2012 05:25 PM, Jon Medhurst (Tixy) wrote:
On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number)
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>
- October 23: ll rebuild based on llct-20121019.<N>, ll code freeze (no
massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Oops.. Your are right. Why don't we have the Thursday, October 32 this year?
So the correct plan is the following:
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
Also, I assume we're not going to try to move to Linux 3.7 this month?
That's correct. We didn't have the kernel.org release based (vs -rc based) ll release for quite a while. And the plan is to stick to v3.6 for 12.10 release unless someone needs to move to v3.7-rc* by all means this cycle. After October 19 the llct tree will move to v3.7-rc*, but the ll tree will be frozen till the 12.10 is out.
That all sounds reasonable to me.
On 10/06/2012 02:37 AM, Andrey Konovalov wrote:
Greetings,
Minor change to the plan:
- The current llct is *llct-20121006.0*
- October 9: ll rebuild based on llct-20121006.0
- October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
I am not in office during this week, so won't be able to update the kernel. Current Samsung LT kernel is based on llct-20121004.0. I will be updating this to llct-20121012.<N> next.
Thanks, Andrey
On 10/05/2012 05:25 PM, Jon Medhurst (Tixy) wrote:
On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number)
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>
- October 23: ll rebuild based on llct-20121019.<N>, ll code freeze
(no massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Oops.. Your are right. Why don't we have the Thursday, October 32 this year?
So the correct plan is the following:
- till the end of this week please use llct-20121004.0 as the base
for the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>, ll code
freeze (no massive ll topics updates after that; bugfixes only)
Also, I assume we're not going to try to move to Linux 3.7 this month?
That's correct. We didn't have the kernel.org release based (vs -rc based) ll release for quite a while. And the plan is to stick to v3.6 for 12.10 release unless someone needs to move to v3.7-rc* by all means this cycle. After October 19 the llct tree will move to v3.7-rc*, but the ll tree will be frozen till the 12.10 is out.
That all sounds reasonable to me.
Hi Tushar,
On 10/08/2012 08:04 AM, Tushar Behera wrote:
On 10/06/2012 02:37 AM, Andrey Konovalov wrote:
Greetings,
Minor change to the plan:
- The current llct is *llct-20121006.0*
- October 9: ll rebuild based on llct-20121006.0
- October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
I am not in office during this week, so won't be able to update the kernel. Current Samsung LT kernel is based on llct-20121004.0. I will be updating this to llct-20121012.<N> next.
This shouldn't be a problem. Thanks for the update!
Andrey
On 10/05/2012 05:25 PM, Jon Medhurst (Tixy) wrote:
On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
> don't we need some kind of notification system where you > announce a plan to rebuild linux-linaro and give us a version of > llct to > base our LT branches off?
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number)
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>
- October 23: ll rebuild based on llct-20121019.<N>, ll code freeze
(no massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Oops.. Your are right. Why don't we have the Thursday, October 32 this year?
So the correct plan is the following: * till the end of this week please use llct-20121004.0 as the base for the linux-linaro (ll) topics * October 9: ll rebuild based on llct-20121005.<N> * October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
Also, I assume we're not going to try to move to Linux 3.7 this month?
That's correct. We didn't have the kernel.org release based (vs -rc based) ll release for quite a while. And the plan is to stick to v3.6 for 12.10 release unless someone needs to move to v3.7-rc* by all means this cycle. After October 19 the llct tree will move to v3.7-rc*, but the ll tree will be frozen till the 12.10 is out.
That all sounds reasonable to me.
Greetings,
On 10/06/2012 01:07 AM, Andrey Konovalov wrote:
Greetings,
Minor change to the plan:
- The current llct is *llct-20121006.0*
- October 9: ll rebuild based on llct-20121006.0
ll-20121010.0 has been pushed to linux-linaro-tracking.git. The pinned manifest is: http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git%3Ba=blob%3Bf...
ll-20121010.0 is based on llct-20121009.0, which is llct-20121006.0 plus few fixes. Here is the pinned manifest: http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git%3Ba=blob%3Bf...
- October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
If you have a new topic to add to 12.10, please make sure that it is submitted by October 12 (common topics to add to llct tree), or October 16 (ll topics). The topics for llct should be based on v3.6 or (if there is a need for that) on another llct topic. The ll topics should be based on llct, or (if there is a need for that) on v3.6 or another ll topic. If an ll topic is based on an older llct version, it can be rebased to the current one automatically, but the commit ids would be mangled (of course).
For the 12.10 the plan is to switch to config fragments for all the supported boards. Please make sure that the config fragment for your board is up-to-date here: git://git.linaro.org/kernel/configs.git , config-boards-3.6 branch
Otherwise these instructions apply: https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelTreeProcess
Thanks, Andrey
On 10/05/2012 05:25 PM, Jon Medhurst (Tixy) wrote:
On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number)
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>
- October 23: ll rebuild based on llct-20121019.<N>, ll code freeze
(no massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Oops.. Your are right. Why don't we have the Thursday, October 32 this year?
So the correct plan is the following:
- till the end of this week please use llct-20121004.0 as the base
for the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>, ll code
freeze (no massive ll topics updates after that; bugfixes only)
Also, I assume we're not going to try to move to Linux 3.7 this month?
That's correct. We didn't have the kernel.org release based (vs -rc based) ll release for quite a while. And the plan is to stick to v3.6 for 12.10 release unless someone needs to move to v3.7-rc* by all means this cycle. After October 19 the llct tree will move to v3.7-rc*, but the ll tree will be frozen till the 12.10 is out.
That all sounds reasonable to me.
Greetings,
If you have a new topic to add to linux-linaro-core-tracking tree in 12.10 release, please make sure that it is submitted by October 12 evening (*tomorrow*). The topics for llct should be based on v3.6 or (if there is a need for that) on another llct topic.
If you have a new topic to add to linux-linaro tree in 12.10 release, please make sure that it is submitted by October 16 evening. The ll topics should be based on llct, or (if there is a need for that) on v3.6 or another ll topic. If an ll topic is based on an older llct version, it can be rebased to the current one automatically, but the commit ids would be mangled (of course). The current llct tree is tagged ll-20121010.0.
For the 12.10 the plan is to switch to config fragments for all the supported boards. To my understanding the boards supported in v3.6 based ll tree are: * vexpress (ARM LT) * origen (Samsung LT) * snowball / u8500 (STE LT) Please let me know if your board is missing from this list.
Please make sure that the config fragment for your board is up-to-date here: git://git.linaro.org/kernel/configs.git , config-boards-3.6 branch (currently it has imx5.conf, omap4.conf (created by Platform team from omap4plus_defconfig present in tilt-3.4), origen.conf, and vexpress64.conf), or in the linux-linaro topic for the board itself (this is the case for vexpress).
Otherwise these instructions apply: https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelTreeProcess
Thanks, Andrey
Greeting,
llct-20121012.0 has been pushed to kernel/linux-linaro-tracking.git Here is the pinned manifest: http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git%3Ba=commitdi...
Minor change to the plan:
- The current llct is *llct-20121006.0*
- October 9: ll rebuild based on llct-20121006.0
ll-20121012.0 has been pushed to kernel/linux-linaro-tracking.git The pinned manifest is: http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git%3Ba=commitdi... This time I tried not using llct as the base for ll-20121012.0 - just the LT's topics have been merged. Very similar to how the llt tree is being built. So the llct version present in ll-20121012.0 depends on what llct tag the LT's topic are based (llct-20121006.0 in this case). This should give more control on the ll tree to the LTs, and should allow the LTs to test their topics with the same llct base which would be in the ll tree (earlier the LT's topics have been merged to a newer llct tree which these topics were not validated with by the LTs, ci testing only). But ll would slip a bit more behind the llct with this approach.
The next important date is: * October 16: ll rebuild based on llct-20121012.0, ll code freeze (no massive ll topics updates after that; bugfixes only)
Thanks, Andrey
On 10/12/2012 12:56 AM, Andrey Konovalov wrote:
Greetings,
If you have a new topic to add to linux-linaro-core-tracking tree in 12.10 release, please make sure that it is submitted by October 12 evening (*tomorrow*). The topics for llct should be based on v3.6 or (if there is a need for that) on another llct topic.
If you have a new topic to add to linux-linaro tree in 12.10 release, please make sure that it is submitted by October 16 evening. The ll topics should be based on llct, or (if there is a need for that) on v3.6 or another ll topic. If an ll topic is based on an older llct version, it can be rebased to the current one automatically, but the commit ids would be mangled (of course). The current llct tree is tagged ll-20121010.0.
For the 12.10 the plan is to switch to config fragments for all the supported boards. To my understanding the boards supported in v3.6 based ll tree are:
- vexpress (ARM LT)
- origen (Samsung LT)
- snowball / u8500 (STE LT)
Please let me know if your board is missing from this list.
Please make sure that the config fragment for your board is up-to-date here: git://git.linaro.org/kernel/configs.git , config-boards-3.6 branch (currently it has imx5.conf, omap4.conf (created by Platform team from omap4plus_defconfig present in tilt-3.4), origen.conf, and vexpress64.conf), or in the linux-linaro topic for the board itself (this is the case for vexpress).
Otherwise these instructions apply: https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelTreeProcess
Thanks, Andrey
Greetings,
The 12.11 linux-linaro kernel release will be v3.7-rc5 or v3.7-rc6 based.
I've tried moving the linux-linaro-core-tracking (llct) tree to v3.7-rc2. With the attached manifest I've got quite some conflicts mostly due to the topics being v3.6 based (conflicts attached): - linaro-android-3.6 has 18 conflicts (conflicts-linux-linaro-core-tracking--Oct25-19:46:28.log) - ubuntu-sauce has 29 conflicts (conflicts-linux-linaro-core-tracking--Oct25-20:34:46.log) - big-LITTLE-MP-v10 has 16 conflicts (conflicts-linux-linaro-core-tracking--Oct25-20:39:02.log)
The armlt-gator topic is on v3.7-rc2 already. Cool!
Please make sure to update your topics to 3.7.
Here is the plan: * October 30: initial v3.7-rc3 based llct build, 3.6 based topics will not be included if there are conflicts * November 6: updated big-LITTLE-MP topic arrives, llct rebuild (llct-20121106) * November 8: linux-linaro (ll) rebuild based on llct-20121106 * November 13: llct rebuild (llct-20121113) * November 15: ll rebuild based on llct-20121113 * November 20: llct rebuild (llct-20121120) * November 22: ll rebuild based on llct-20121120, ll code freeze (no massive ll topics updates after that; bugfixes only)
(The dates above are milestones, there will be additional llct/ll rebuilds on other dates as well)
The config fragment branches to be used in 12.11: git://git.linaro.org/kernel/configs.git , config-core-tracking and config-boards-tracking branches.
Thanks, Andrey
Greetings,
This cycle some more attention is given to the shape of the ci builds done from the llct tree (the ones with "llct" in their name at https://ci.linaro.org/jenkins/view/Linux%20Linaro%20Tracking/). See below.
On 10/27/2012 12:39 PM, Andrey Konovalov wrote:
The 12.11 linux-linaro kernel release will be v3.7-rc5 or v3.7-rc6 based.
Please make sure to update your topics to 3.7.
Here is the plan:
- October 30: initial v3.7-rc3 based llct build, 3.6 based topics will
not be included if there are conflicts
Done. The tag is llct-20121101.1. v3.7-rc3 based.
Origen failed to boot in LAVA (silence after "Uncompressing Linux... done, booting the kernel.") mmc doesn't work on Panda when the kernel is built using the (old) config fragments (http://validation.linaro.org/lava-server/scheduler/job/37832/log_file). Panda boots ok with omap2plus_defconfig. vexpress boots ok.
- November 6: updated big-LITTLE-MP topic arrives, llct rebuild
(llct-20121106)
Done. The tag is llct-20121106.0. v3.7-rc4 based.
Android and big-LITTLE-MP topics are back. New Gator version (v5.12).
*ubuntu-sauce topic will be dropped* Anyone objects?
The same boot failure for Origen. Disabling device tree in the kernel config makes the kernel to start booting (http://validation.linaro.org/lava-server/scheduler/job/37885/log_file). Could be arch/arm/boot/dts/exynos4210-origen.dts issue.
Thanks, Andrey
- November 8: linux-linaro (ll) rebuild based on llct-20121106
- November 13: llct rebuild (llct-20121113)
- November 15: ll rebuild based on llct-20121113
- November 20: llct rebuild (llct-20121120)
- November 22: ll rebuild based on llct-20121120, ll code freeze (no
massive ll topics updates after that; bugfixes only)
(The dates above are milestones, there will be additional llct/ll rebuilds on other dates as well)
The config fragment branches to be used in 12.11: git://git.linaro.org/kernel/configs.git , config-core-tracking and config-boards-tracking branches.
Thanks, Andrey
On Wed, 2012-11-07 at 00:10 +0400, Andrey Konovalov wrote:
- November 6: updated big-LITTLE-MP topic arrives, llct rebuild
(llct-20121106)
Done. The tag is llct-20121106.0. v3.7-rc4 based.
Android and big-LITTLE-MP topics are back. New Gator version (v5.12).
*ubuntu-sauce topic will be dropped* Anyone objects?
Definitely no objection from me :-) Ubuntu appears to work fine without that topic and rebasing and forward porting it just seemed to add bugs.
On 11/07/2012 01:40 AM, Andrey Konovalov wrote:
Greetings,
This cycle some more attention is given to the shape of the ci builds done from the llct tree (the ones with "llct" in their name at https://ci.linaro.org/jenkins/view/Linux%20Linaro%20Tracking/). See below.
On 10/27/2012 12:39 PM, Andrey Konovalov wrote:
The 12.11 linux-linaro kernel release will be v3.7-rc5 or v3.7-rc6 based.
Please make sure to update your topics to 3.7.
Here is the plan:
- October 30: initial v3.7-rc3 based llct build, 3.6 based topics will
not be included if there are conflicts
Done. The tag is llct-20121101.1. v3.7-rc3 based.
Origen failed to boot in LAVA (silence after "Uncompressing Linux... done, booting the kernel.")
I haven't tested it yet (llct), but it might be because of incorrect serial port number. I have tested v3.7-rc4 kernel with said change in config file, it works. Anyways, I will get back tomorrow after testing llct.
mmc doesn't work on Panda when the kernel is built using the (old) config fragments (http://validation.linaro.org/lava-server/scheduler/job/37832/log_file). Panda boots ok with omap2plus_defconfig. vexpress boots ok.
- November 6: updated big-LITTLE-MP topic arrives, llct rebuild
(llct-20121106)
Done. The tag is llct-20121106.0. v3.7-rc4 based.
Android and big-LITTLE-MP topics are back. New Gator version (v5.12).
*ubuntu-sauce topic will be dropped* Anyone objects?
The same boot failure for Origen. Disabling device tree in the kernel config makes the kernel to start booting (http://validation.linaro.org/lava-server/scheduler/job/37885/log_file). Could be arch/arm/boot/dts/exynos4210-origen.dts issue.
Thanks, Andrey
- November 8: linux-linaro (ll) rebuild based on llct-20121106
- November 13: llct rebuild (llct-20121113)
- November 15: ll rebuild based on llct-20121113
- November 20: llct rebuild (llct-20121120)
- November 22: ll rebuild based on llct-20121120, ll code freeze (no
massive ll topics updates after that; bugfixes only)
(The dates above are milestones, there will be additional llct/ll rebuilds on other dates as well)
The config fragment branches to be used in 12.11: git://git.linaro.org/kernel/configs.git , config-core-tracking and config-boards-tracking branches.
Thanks, Andrey
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On 11/07/12 19:52, the mail apparently from Tushar Behera included:
On 11/07/2012 01:40 AM, Andrey Konovalov wrote:
Greetings,
This cycle some more attention is given to the shape of the ci builds done from the llct tree (the ones with "llct" in their name at https://ci.linaro.org/jenkins/view/Linux%20Linaro%20Tracking/). See below.
On 10/27/2012 12:39 PM, Andrey Konovalov wrote:
The 12.11 linux-linaro kernel release will be v3.7-rc5 or v3.7-rc6 based.
Please make sure to update your topics to 3.7.
Here is the plan:
- October 30: initial v3.7-rc3 based llct build, 3.6 based topics will
not be included if there are conflicts
Done. The tag is llct-20121101.1. v3.7-rc3 based.
Origen failed to boot in LAVA (silence after "Uncompressing Linux... done, booting the kernel.")
I haven't tested it yet (llct), but it might be because of incorrect serial port number. I have tested v3.7-rc4 kernel with said change in config file, it works. Anyways, I will get back tomorrow after testing llct.
FWIW we are currently retargeting on 3.7-rc4 I think + llct and then tracking.
So there might be more than one "hundreds of arch-specific patches" LT kernels based on llct to bind together this time, making ll more than theoretically useful.
-Andy
mmc doesn't work on Panda when the kernel is built using the (old) config fragments (http://validation.linaro.org/lava-server/scheduler/job/37832/log_file). Panda boots ok with omap2plus_defconfig. vexpress boots ok.
- November 6: updated big-LITTLE-MP topic arrives, llct rebuild
(llct-20121106)
Done. The tag is llct-20121106.0. v3.7-rc4 based.
Android and big-LITTLE-MP topics are back. New Gator version (v5.12).
*ubuntu-sauce topic will be dropped* Anyone objects?
The same boot failure for Origen. Disabling device tree in the kernel config makes the kernel to start booting (http://validation.linaro.org/lava-server/scheduler/job/37885/log_file). Could be arch/arm/boot/dts/exynos4210-origen.dts issue.
Thanks, Andrey
- November 8: linux-linaro (ll) rebuild based on llct-20121106
- November 13: llct rebuild (llct-20121113)
- November 15: ll rebuild based on llct-20121113
- November 20: llct rebuild (llct-20121120)
- November 22: ll rebuild based on llct-20121120, ll code freeze (no
massive ll topics updates after that; bugfixes only)
(The dates above are milestones, there will be additional llct/ll rebuilds on other dates as well)
The config fragment branches to be used in 12.11: git://git.linaro.org/kernel/configs.git , config-core-tracking and config-boards-tracking branches.
Thanks, Andrey
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Greetings,
The first, very initial v3.7-rc4 based ll tree is out, the tag is ll-20121108.0 It has just one topic: integration-linaro-vexpress from the ARM LT.
The current 12.11 schedule is now: * October 30: initial v3.7-rc3 based llct build, 3.6 based topics will not be included if there are conflicts - Done. The tag is llct-20121101.1. v3.7-rc3 based. * November 6: updated big-LITTLE-MP topic arrives, llct rebuild (llct-20121106) - Done. The tag is llct-20121106.0. v3.7-rc4 based. * November 8: linux-linaro (ll) rebuild based on llct-20121106 - Done. The tag is ll-20121108.0 * November 13: llct rebuild (llct-20121113) - Expected updates: . android perf patch from Bernhard Rosenkraenzer (patch received, but no topic branch yet), . devfreq patches from Rajagopal Venkat (waiting for the topic branch) * November 15: ll rebuild based on llct-20121113 * November 20: llct rebuild (llct-20121120) * November 22: ll rebuild based on llct-20121120, ll code freeze (no massive ll topics updates after that; bugfixes only)
Thanks, Andrey
This cycle some more attention is given to the shape of the ci builds done from the llct tree (the ones with "llct" in their name at https://ci.linaro.org/jenkins/view/Linux%20Linaro%20Tracking/). See below.
On 10/27/2012 12:39 PM, Andrey Konovalov wrote:
The 12.11 linux-linaro kernel release will be v3.7-rc5 or v3.7-rc6 based.
Please make sure to update your topics to 3.7.
Here is the plan:
- October 30: initial v3.7-rc3 based llct build, 3.6 based topics will
not be included if there are conflicts
Done. The tag is llct-20121101.1. v3.7-rc3 based.
Origen failed to boot in LAVA (silence after "Uncompressing Linux... done, booting the kernel.") mmc doesn't work on Panda when the kernel is built using the (old) config fragments (http://validation.linaro.org/lava-server/scheduler/job/37832/log_file). Panda boots ok with omap2plus_defconfig. vexpress boots ok.
- November 6: updated big-LITTLE-MP topic arrives, llct rebuild
(llct-20121106)
Done. The tag is llct-20121106.0. v3.7-rc4 based.
Android and big-LITTLE-MP topics are back. New Gator version (v5.12).
*ubuntu-sauce topic will be dropped* Anyone objects?
The same boot failure for Origen. Disabling device tree in the kernel config makes the kernel to start booting (http://validation.linaro.org/lava-server/scheduler/job/37885/log_file). Could be arch/arm/boot/dts/exynos4210-origen.dts issue.
Thanks, Andrey
- November 8: linux-linaro (ll) rebuild based on llct-20121106
- November 13: llct rebuild (llct-20121113)
- November 15: ll rebuild based on llct-20121113
- November 20: llct rebuild (llct-20121120)
- November 22: ll rebuild based on llct-20121120, ll code freeze (no
massive ll topics updates after that; bugfixes only)
(The dates above are milestones, there will be additional llct/ll rebuilds on other dates as well)
The config fragment branches to be used in 12.11: git://git.linaro.org/kernel/configs.git , config-core-tracking and config-boards-tracking branches.
Thanks, Andrey
Greetings,
The linux-linaro-core-tracking tree has been updated to v3.7-rc5.
The current 12.11 schedule is now: * October 30: initial v3.7-rc3 based llct build, 3.6 based topics will not be included if there are conflicts - Done. The tag is llct-20121101.1. v3.7-rc3 based. * November 6: updated big-LITTLE-MP topic arrives, llct rebuild (llct-20121106) - Done. The tag is llct-20121106.0. v3.7-rc4 based. * November 8: linux-linaro (ll) rebuild based on llct-20121106 - Done. The tag is ll-20121108.0 * November 13: llct rebuild (llct-20121113) - Done. The tag is llct-20121113.0. v3.7-rc5 based. Otherwise the only change is in the "configs" topic: babf06c configs: linaro-base: set CONFIG_AEABI=y * November 15: ll rebuild based on llct-20121113 * November 20: llct rebuild (llct-20121120) - Expected updates: . android perf patch from Bernhard Rosenkraenzer (patch received, but no topic branch yet), . devfreq patches from Rajagopal Venkat (waiting for the updated topic branch) * November 22: ll rebuild based on llct-20121120, ll code freeze (no massive ll topics updates after that; bugfixes only)
Thanks, Andrey
Greetings,
The linux-linaro-core-tracking tree has been updated to v3.7-rc6.
The current 12.11 schedule is now: * October 30: initial v3.7-rc3 based llct build, 3.6 based topics will not be included if there are conflicts - Done. The tag is llct-20121101.1. v3.7-rc3 based. * November 6: updated big-LITTLE-MP topic arrives, llct rebuild (llct-20121106) - Done. The tag is llct-20121106.0. v3.7-rc4 based. * November 8: linux-linaro (ll) rebuild based on llct-20121106 - Done. The tag is ll-20121108.0 * November 13: llct rebuild (llct-20121113) - Done. The tag is llct-20121113.0. v3.7-rc5 based. Otherwise the only change is in the "configs" topic: babf06c configs: linaro-base: set CONFIG_AEABI=y * November 15: ll rebuild based on llct-20121113 - Done. The tag is ll-20121115.0. Origen support is back into the ll tree (the "tracking" topic from the Samsung LT). * November 20: llct rebuild (llct-20121120) - Done. The tag is llct-20121120.1. v3.7-rc6 based. This is the last scheduled llct update for 12.11. - Updates: . new version of the big.LITTLE-MP topic (big-LITTLE-MP-master-v12), . configs topic renamed to core-configs, . basic-board-configs topic added, . devfreq patches from Rajagopal Venkat added . "KBuild: Allow scripts/* to be cross compiled" patch added to llct-v3.7-misc-fixes topic - Not included into llct-20121120.1: . android perf patch from Bernhard Rosenkraenzer (patch received, but no topic branch yet): too much conflicts in tools/perf/Makefile vs v3.7-rc6 for me to resolve myself. If I get the version of this patch to apply cleanly to v3.7-rc6, it could be included right into the ll tree for 12.11. (The risk is low, as the patch makes no changes outside tools/perf). * November 22: ll rebuild based on llct-20121120.1, ll code freeze (no massive ll topics updates after that; bugfixes only)
Thanks, Andrey
Greetings,
The linux-linaro-core-tracking tree has been updated to v3.7-rc6.
The current 12.11 schedule is now: * October 30: initial v3.7-rc3 based llct build, 3.6 based topics will not be included if there are conflicts - Done. The tag is llct-20121101.1. v3.7-rc3 based. * November 6: updated big-LITTLE-MP topic arrives, llct rebuild (llct-20121106) - Done. The tag is llct-20121106.0. v3.7-rc4 based. * November 8: linux-linaro (ll) rebuild based on llct-20121106 - Done. The tag is ll-20121108.0 * November 13: llct rebuild (llct-20121113) - Done. The tag is llct-20121113.0. v3.7-rc5 based. Otherwise the only change is in the "configs" topic: babf06c configs: linaro-base: set CONFIG_AEABI=y * November 15: ll rebuild based on llct-20121113 - Done. The tag is ll-20121115.0. Origen support is back into the ll tree (the "tracking" topic from the Samsung LT). * November 20: llct rebuild (llct-20121120) - Done. The tag is llct-20121120.1. v3.7-rc6 based. This is the last scheduled llct update for 12.11. - Updates: . new version of the big.LITTLE-MP topic (big-LITTLE-MP-master-v12), . configs topic renamed to core-configs, . basic-board-configs topic added, . devfreq patches from Rajagopal Venkat added . "KBuild: Allow scripts/* to be cross compiled" patch added to llct-v3.7-misc-fixes topic - Not included into llct-20121120.1: . android perf patch from Bernhard Rosenkraenzer (patch received, but no topic branch yet): too much conflicts in tools/perf/Makefile vs v3.7-rc6 for me to resolve myself. If I get the version of this patch to apply cleanly to v3.7-rc6, it could be included right into the ll tree for 12.11. (The risk is low, as the patch makes no changes outside tools/perf). * November 23: ll rebuild based on llct-20121120.1, ll code freeze (no massive ll topics updates after that; bugfixes only) - Done. The tag is ll-20121123.2. No more ll updates for 12.11 unless critical issues are found. Updates: . based on llct-20121120.1 . android perf patch from Bernhard Rosenkraenzer. Not the latest version unfortunately, as it arrived too late for 12.11. In 12.12 the most recent version of this patch will go into llct.
Thanks, Andrey
Greetings,
The current 12.12 schedule has been published on wiki:
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule
This is a short cycle: the linux-linaro (ll) tree freeze is December 13.
llct has been updated to v3.7-rc8, the tag is llct-20121205.0 Tomorrow I'll rebuild the ll using llct-20121205.0 as the base.
Thanks, Andrey
Greetings,
The 12.12 schedule has been updated on wiki:
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule
Both the llct and the ll trees have been updated (see the wiki page for the details).
There should be no more planned updates to llct for 12.12 release except moving from v3.7-rc8 to v3.7 release if Linus makes it tonight.
Beware: this Thursday is the code freeze for linux-linaro kernel tree!
Thanks, Andrey
10.12.2012 23:26, Andrey Konovalov пишет:
Greetings,
The 12.12 schedule has been updated on wiki:
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule
Both the llct and the ll trees have been updated (see the wiki page for the details).
There should be no more planned updates to llct for 12.12 release except moving from v3.7-rc8 to v3.7 release if Linus makes it tonight.
The llct based on v3.7 release is there, and is tagged llct-20121211.0
Thanks, Andrey
On Tue, Dec 11, 2012 at 09:54:19AM +0000, Andrey Konovalov wrote:
10.12.2012 23:26, Andrey Konovalov пишет:
Greetings,
The 12.12 schedule has been updated on wiki:
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule
Both the llct and the ll trees have been updated (see the wiki page for the details).
There should be no more planned updates to llct for 12.12 release except moving from v3.7-rc8 to v3.7 release if Linus makes it tonight.
The llct based on v3.7 release is there, and is tagged llct-20121211.0
Isn't the tag supposed to be llct-20121212.0? I'm getting confused between release codes and December days.
Regards, Liviu
Thanks, Andrey
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On 12/11/2012 06:13 PM, Liviu Dudau wrote:
On Tue, Dec 11, 2012 at 09:54:19AM +0000, Andrey Konovalov wrote:
10.12.2012 23:26, Andrey Konovalov пишет:
Greetings,
The 12.12 schedule has been updated on wiki:
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule
Both the llct and the ll trees have been updated (see the wiki page for the details).
There should be no more planned updates to llct for 12.12 release except moving from v3.7-rc8 to v3.7 release if Linus makes it tonight.
The llct based on v3.7 release is there, and is tagged llct-20121211.0
Isn't the tag supposed to be llct-20121212.0? I'm getting confused between release codes and December days.
This tag is llct-YYYYMMDD.X where YYYMMDD is the date when the tree has been "rebuilt". This is not related to the release codes. The release will be tagged using different format like linux-linaro-3.7-2012.12 (<tree name>-<kernel version>-<release code>).
Thanks, Andrey
Regards, Liviu
Thanks, Andrey
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Greetings,
The ll tree has been updated to use llct-20121211.0 as the base. It still has just the ARM LT topic; waiting for the v3.7 based topic from Samsung LT. Also the hack by Bero to make perf to build on android has been removed: will see if it break the perf build on ubuntu (see the LinuxLinaroKernelSchedule for more details).
* December 13 is the last date to update ll for 12.12 *
The current status and the schedule is: https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule
Thanks, Andrey
On 12/11/2012 01:54 PM, Andrey Konovalov wrote:
The llct based on v3.7 release is there, and is tagged llct-20121211.0
On 12/13/2012 02:14 AM, Andrey Konovalov wrote:
Greetings,
The ll tree has been updated to use llct-20121211.0 as the base. It still has just the ARM LT topic; waiting for the v3.7 based topic from Samsung LT.
v3.7 based Samsung LT kernel has been pushed to glo. [1]
[1] http://git.linaro.org/gitweb?p=landing-teams/working/samsung/kernel.git%3Ba=...
Issues: * Ethernet still broken on Ubuntu. (Same status as 3.7-rc6, interesting Android kernel built from the same source has working ethernet connection.) * Android kernel doesn't compile because of some change in gpu/ion. Even after adding fixes for compilation errors there is crash during booting, so didn't push those fixes.
I hope we will have some more time for any critical fixes.
Also the hack by Bero to make perf to build on android has been removed: will see if it break the perf build on ubuntu (see the LinuxLinaroKernelSchedule for more details).
- December 13 is the last date to update ll for 12.12 *
The current status and the schedule is: https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule
Thanks, Andrey
On 12/11/2012 01:54 PM, Andrey Konovalov wrote:
The llct based on v3.7 release is there, and is tagged llct-20121211.0
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On 12/13/2012 03:53 AM, Tushar Behera wrote:
- Android kernel doesn't compile because of some change in gpu/ion. Even
after adding fixes for compilation errors there is crash during booting, so didn't push those fixes.
Tushar: Sorry about this. I'll try to take a look at the compilation issues today (mind sending me your config?). I've not yet applied the patches you sent as I wanted to double check that AOSP didn't have more official fixes. Will try to get this sorted here quickly.
thanks -john
On 12/13/2012 03:53 AM, Tushar Behera wrote:
- Android kernel doesn't compile because of some change in gpu/ion. Even
after adding fixes for compilation errors there is crash during booting, so didn't push those fixes.
Hey Tushar, After looking at the issues you pointed out, I've got some alternative patches to try to resolve the ION issues.
Would you mind trying them out? I don't have any ion supported hardware around, so I'm not able to actually test if they're ok, but they do build.
See the changes here: http://git.linaro.org/gitweb?p=people/jstultz/android.git%3Ba=shortlog%3Bh=r...
Or fetch them here: git://git.linaro.org/people/jstultz/android.git tushar-test
If they work for you, I'll push them to the Linaro+Android tree.
thanks -john
On 10/06/2012 02:37 AM, Andrey Konovalov wrote:
Greetings,
Minor change to the plan:
- The current llct is *llct-20121006.0*
- October 9: ll rebuild based on llct-20121006.0
- October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
Samsung LT kernel tree based on llct-20121012.0 has been pushed to g.l.o.
git://git.linaro.org/landing-teams/working/samsung/kernel.git branch: tracking tag: samsung-lt-v3.6-1
Let me know if there are issues after building linux-linaro tree. I would be out of office for rest of the week and would be checking the mails on coming Monday.
Thanks, Andrey
On 10/05/2012 05:25 PM, Jon Medhurst (Tixy) wrote:
On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number)
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>
- October 23: ll rebuild based on llct-20121019.<N>, ll code freeze
(no massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Oops.. Your are right. Why don't we have the Thursday, October 32 this year?
So the correct plan is the following:
- till the end of this week please use llct-20121004.0 as the base
for the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>, ll code
freeze (no massive ll topics updates after that; bugfixes only)
Also, I assume we're not going to try to move to Linux 3.7 this month?
That's correct. We didn't have the kernel.org release based (vs -rc based) ll release for quite a while. And the plan is to stick to v3.6 for 12.10 release unless someone needs to move to v3.7-rc* by all means this cycle. After October 19 the llct tree will move to v3.7-rc*, but the ll tree will be frozen till the 12.10 is out.
That all sounds reasonable to me.
On 10/17/2012 10:41 AM, Tushar Behera wrote:
On 10/06/2012 02:37 AM, Andrey Konovalov wrote:
Greetings,
Minor change to the plan:
- The current llct is *llct-20121006.0*
- October 9: ll rebuild based on llct-20121006.0
- October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
Samsung LT kernel tree based on llct-20121012.0 has been pushed to g.l.o.
git://git.linaro.org/landing-teams/working/samsung/kernel.git branch: tracking tag: samsung-lt-v3.6-1
Let me know if there are issues after building linux-linaro tree. I would be out of office for rest of the week and would be checking the mails on coming Monday.
I've created ll-20121017.0 using the updated Samsung LT's tracking topic. The difference from the previous topic version is dropping the two commits: "UBUNTU: dm-raid4-5: Fix compilation warning" and "CONFIG: ORIGEN: ANDROID: Disable HDMI/FIMC temporarily" I've restored the "UBUNTU: dm-raid4-5: Fix compilation warning" one, as it seems to be the correct fix. So the resulting difference between ll-20121016.0 and ll-20121017.0 is just the android_origen_defconfig change:
diff --git a/arch/arm/configs/android_origen_defconfig b/arch/arm/configs/android_origen_defconfig index d04cf03..869183e 100644 --- a/arch/arm/configs/android_origen_defconfig +++ b/arch/arm/configs/android_origen_defconfig @@ -125,6 +125,11 @@ CONFIG_VIDEO_S5K4ECGX_SLSI_4EC=y CONFIG_V4L_PLATFORM_DRIVERS=y CONFIG_V4L_USB_DRIVERS=y CONFIG_VIDEO_SAMSUNG_S5P_FIMC=y +CONFIG_VIDEO_S5P_FIMC=y +CONFIG_VIDEO_SAMSUNG_S5P_TV=y +CONFIG_VIDEO_SAMSUNG_S5P_HDMI=y +CONFIG_VIDEO_SAMSUNG_S5P_SDO=y +CONFIG_VIDEO_SAMSUNG_S5P_MIXER=y CONFIG_V4L_MEM2MEM_DRIVERS=y CONFIG_VIDEO_SAMSUNG_S5P_G2D=y CONFIG_VIDEO_SAMSUNG_S5P_JPEG=y
Thanks, Andrey
On 10/05/2012 05:25 PM, Jon Medhurst (Tixy) wrote:
On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
> don't we need some kind of notification system where you > announce a plan to rebuild linux-linaro and give us a version of > llct to > base our LT branches off?
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number)
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>
- October 23: ll rebuild based on llct-20121019.<N>, ll code freeze
(no massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Oops.. Your are right. Why don't we have the Thursday, October 32 this year?
So the correct plan is the following: * till the end of this week please use llct-20121004.0 as the base for the linux-linaro (ll) topics * October 9: ll rebuild based on llct-20121005.<N> * October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
Also, I assume we're not going to try to move to Linux 3.7 this month?
That's correct. We didn't have the kernel.org release based (vs -rc based) ll release for quite a while. And the plan is to stick to v3.6 for 12.10 release unless someone needs to move to v3.7-rc* by all means this cycle. After October 19 the llct tree will move to v3.7-rc*, but the ll tree will be frozen till the 12.10 is out.
That all sounds reasonable to me.
On 17 October 2012 21:26, Andrey Konovalov andrey.konovalov@linaro.org wrote:
On 10/17/2012 10:41 AM, Tushar Behera wrote:
On 10/06/2012 02:37 AM, Andrey Konovalov wrote:
Greetings,
Minor change to the plan:
- The current llct is *llct-20121006.0*
- October 9: ll rebuild based on llct-20121006.0
- October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
Samsung LT kernel tree based on llct-20121012.0 has been pushed to g.l.o.
git://git.linaro.org/landing-teams/working/samsung/kernel.git branch: tracking tag: samsung-lt-v3.6-1
Let me know if there are issues after building linux-linaro tree. I would be out of office for rest of the week and would be checking the mails on coming Monday.
I've created ll-20121017.0 using the updated Samsung LT's tracking topic. The difference from the previous topic version is dropping the two commits: "UBUNTU: dm-raid4-5: Fix compilation warning" and "CONFIG: ORIGEN: ANDROID: Disable HDMI/FIMC temporarily" I've restored the "UBUNTU: dm-raid4-5: Fix compilation warning" one, as it seems to be the correct fix.
Thanks. This patch needs to picked up in ubuntu-sauce branch.
So the resulting difference between ll-20121016.0 and ll-20121017.0 is just the android_origen_defconfig change:
That is right.
diff --git a/arch/arm/configs/android_origen_defconfig b/arch/arm/configs/android_origen_defconfig index d04cf03..869183e 100644 --- a/arch/arm/configs/android_origen_defconfig +++ b/arch/arm/configs/android_origen_defconfig @@ -125,6 +125,11 @@ CONFIG_VIDEO_S5K4ECGX_SLSI_4EC=y CONFIG_V4L_PLATFORM_DRIVERS=y CONFIG_V4L_USB_DRIVERS=y CONFIG_VIDEO_SAMSUNG_S5P_FIMC=y +CONFIG_VIDEO_S5P_FIMC=y +CONFIG_VIDEO_SAMSUNG_S5P_TV=y +CONFIG_VIDEO_SAMSUNG_S5P_HDMI=y +CONFIG_VIDEO_SAMSUNG_S5P_SDO=y +CONFIG_VIDEO_SAMSUNG_S5P_MIXER=y CONFIG_V4L_MEM2MEM_DRIVERS=y CONFIG_VIDEO_SAMSUNG_S5P_G2D=y CONFIG_VIDEO_SAMSUNG_S5P_JPEG=y
Thanks, Andrey
On 10/05/2012 05:25 PM, Jon Medhurst (Tixy) wrote:
On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote: >> >> don't we need some kind of notification system where you >> announce a plan to rebuild linux-linaro and give us a version of >> llct to >> base our LT branches off? > > > Yes, this makes sense. > Would the following plan be OK: > (<N> should normally be 0, but may be a small positive number) > * till the end of this week please use llct-20121004.0 as the base > for > the linux-linaro (ll) topics > * October 9: ll rebuild based on llct-20121005.<N> > * October 16: ll rebuild based on llct-20121012.<N> > * October 23: ll rebuild based on llct-20121019.<N>, ll code freeze > (no > massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Oops.. Your are right. Why don't we have the Thursday, October 32 this year?
So the correct plan is the following: * till the end of this week please use llct-20121004.0 as the base for the linux-linaro (ll) topics * October 9: ll rebuild based on llct-20121005.<N> * October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
Also, I assume we're not going to try to move to Linux 3.7 this month?
That's correct. We didn't have the kernel.org release based (vs -rc based) ll release for quite a while. And the plan is to stick to v3.6 for 12.10 release unless someone needs to move to v3.7-rc* by all means this cycle. After October 19 the llct tree will move to v3.7-rc*, but the ll tree will be frozen till the 12.10 is out.
That all sounds reasonable to me.
On Fri, Oct 5, 2012 at 2:03 PM, Andrey Konovalov andrey.konovalov@linaro.org wrote:
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Andrey, let's make sure this is properly communicated over time for the maintainers and linaro-dev, so everyone can understand and see the progress done (to prepare any kind of rebase/pull).
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number)
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>
- October 23: ll rebuild based on llct-20121019.<N>, ll code freeze (no
massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Oops.. Your are right. Why don't we have the Thursday, October 32 this year?
:-)
So the correct plan is the following:
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
October 9: ll rebuild based on llct-20121005.<N>
October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no
massive ll topics updates after that; bugfixes only)
Also, I assume we're not going to try to move to Linux 3.7 this month?
That's correct. We didn't have the kernel.org release based (vs -rc based) ll release for quite a while. And the plan is to stick to v3.6 for 12.10 release unless someone needs to move to v3.7-rc* by all means this cycle. After October 19 the llct tree will move to v3.7-rc*, but the ll tree will be frozen till the 12.10 is out.
There are some advantages already about using v3.7 (like aarch64 support), but as it's a quite short cycle, and the we'll probably not have enough RCs to produce a useful tree for the release, v3.6 would be the best option.
Let's also make sure we have a session at Connect to discuss the tree maintenance as usual, then we can better announce/propose any changes you're doing for the following cycles.
Cheers,
On 06/10/12 08:52, the mail apparently from Ricardo Salveti included:
On Fri, Oct 5, 2012 at 2:03 PM, Andrey Konovalov andrey.konovalov@linaro.org wrote:
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Andrey, let's make sure this is properly communicated over time for the maintainers and linaro-dev, so everyone can understand and see the progress done (to prepare any kind of rebase/pull).
If Andrey keeps llct reasonably following Linus HEAD (as he has been, kudos) - and keep a nice llc-3.6 with 3.6 stable pieces and any critical backport fix for other llct content appearing on it in parallel - you'll be solving everything needed on TILT side.
Also, I assume we're not going to try to move to Linux 3.7 this month?
That's correct. We didn't have the kernel.org release based (vs -rc based)
Our plan is retarget on 3.6 basis next week and before long generate a tilt-3.6.
-Andy
-
Andrey Konovalov -
Andy Green -
John Stultz -
Jon Medhurst (Tixy) -
Liviu Dudau -
Ricardo Salveti -
Tushar Behera