On 09/11/2013 06:09 PM, Mark Brown wrote:
On 11 September 2013 11:07, Jon Medhurst (Tixy) <tixy@linaro.org mailto:tixy@linaro.org> wrote:
On Wed, 2013-09-11 at 10:51 +0100, Mark Brown wrote: > Either works, though you should apply the patch on one of the topic > branches then merge that into the LSK branches - probably the warnings > branch is best here. Or the topic branch with the patch which introduces the warning? I.e. v3.10/topic/tc2 which has bba0859a996589e9673717864d104a7603687941 It's Mark's call though.
Yes, if it actually depends on the TC2 changes it'll need to go on that branch.
Are these topic/xxx branch used for testing purpose for formal lsk? Actually, the tc2 branch has much compilation bugs with lsk kernel config. So, could you push a new topic branch for this patch testing purpose? or forcefully covered the warning branch with lsk + this patch?