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.
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
