Re: [PATCH] recipes-kernel: Add GLSDK specific kernel tree for omap-a15

[Siddharth Heroor <heroor@ti.com>]

On 6/27/2013 7:53 PM, Denys Dmytriyenko wrote:
>>> +
>>> +S = "${WORKDIR}/git"
>>> +
>>> +BRANCH = "master"
>>> +
>>> +# This commit corresponds to ti2013.04.02 release tag
>>
>> Sorry to nit-pick here, but any reason to re-use the tag name from the 
>> linux-ti-staging tree?  The reason I ask is back to it being confusing if I 
>> have two trees with the same tag name (including version) it becomes kind of 
>> confusing.  Especially since this tree is part of the same git.ti.com 
>> project as the other one.  Thoughts?
> 
> Currently, it's just an identical copy of our LCPD tree w/o any patches on 
> top, so it has the same tags and commit IDs...
> 
> One can argue though, if the trees are still the same, what's the reason to 
> create a new recipe so early in advance?

I want to get the basic recipes in place in time for the release. We do
have the option of submitting recipes post the release but I want to
avoid that.

Having the recipes in meta-ti ahead of time allows us to get feedback
_before_ we freeze.

> 
> 
>>> +SRCREV = "f3cb62a800ae37f17a3382b10d155ee02dbc83fc"
>>> +PV = "3.8.13"
>>> +
>>> +# Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause
>>> a rebuild
>>> +MACHINE_KERNEL_PR_append = "f+gitr${SRCPV}"
>>
>> Go ahead and reset your append here to a+ gitr${SRCPV}.  No need to start 
>> from f.
>>
>> Thanks for the submission.  Overall looks pretty good, just a few things to 
>> fix up.
> 
> +1 keep up the good work!
>