On 01/27/2014 09:50 AM, Dominig ar Foll (Intel OTC) wrote: > Hello, > > I see in that some of us would like to integrate very early features in > Tizen Kernel while some other would prefer to remain conservative. > In order to agree on a common model, I would like to propose the > following simple concepts.
Should external/out-of-tree kernel modules be somehow addressed in such proposal too? > - Only patches accepted in a published 'release' Linux Kernel can be > used in Tizen Base/Common > - Kernel source should be common for all verticals, but Kernel config > is vertical specific. Łukasz Stelmach proposed this already, please see Artem's response https://lists.tizen.org/pipermail/dev/2013-December/001335.html > - Tizen Generic (which is only a development tool) will follow that rule. > - Back-ported patches accepted in a more recent 'release' of the kernel > are acceptable in Tizen Base/Common > - Vertical may decide to use non "released" patches but that is not > advisable. > - Platform integrator remain free of their implementation as long as it > complies with their vertical requirements. > > That model should allow us to remain agile, while protecting us to > introduce fork from the kernel main line and to create a maintenance > nightmare. Cheers, Karol _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
