On Fri, Apr 1, 2011 at 11:57 PM, Philippe Robin philippe.robin@arm.com wrote:
Eric,
So maybe it's just a right time to talk about using linaro ARM kernel tree as a fork for quick merge of the ever expanding SoC and board support, and using it more as a productive kernel for downstream.
I don't think that a 'fork' is really a solution we are looking for. Using Linaro as a staging and consolidation tree and at the same time improving the upstream kernel is more what I would be looking for and what Linaro is currently working on.
Yeah, staging is more close to what I meant, a 'fork' is not appropriate here, as getting the support into mainline will always be our goal. Yet there seems to be necessary to have such a temporary place for those patches to live before the mainline is in a good enough shape. And it should not be an arm-next tree, which is just for detecting merge conflict. I expect it to be more usable, end users can just download and build a basically usable kernel.
Regards, Philippe
-----Original Message----- From: linaro-dev-bounces@lists.linaro.org [mailto:linaro-dev-bounces@lists.linaro.org] On Behalf Of Eric Miao Sent: 01 April 2011 16:44 To: Linaro Dev Subject: Linus being annoyed by the ARM kernel code
Just FYI - lengthy but very interesting read, Linus was really good at wording, enjoy heh :-)
https://lkml.org/lkml/2011/3/17/283
So maybe it's just a right time to talk about using linaro ARM kernel tree as a fork for quick merge of the ever expanding SoC and board support, and using it more as a productive kernel for downstream. And in the mean time, improve the mainline kernel into such a good shape that with less crappy code we could support more platforms?
Just a bit thought on that possibility.
- eric
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev