On Fri, Dec 4, 2015 at 4:47 PM, Daniel Thompson daniel.thompson@linaro.org wrote:
On 02/12/15 20:27, Geoff Levand wrote:
Hi,
On Tue, 2015-11-24 at 00:03 +0800, Guodong Xu wrote:
On 23 November 2015 at 21:14, Steve Capper steve.capper@linaro.org wrote:
I have been unable to do any meaningful work with my Hikey board because I haven't been able to work with a mainline kernel on it. Hopefully this will soon improve.
We have a hikey mainline branch now. It based on v4.3, plus several topics which are not accepted yet.
https://github.com/96boards/linux/tree/hikey-mainline-rebase
This is a rebase tree, with tracking mainline as its target.
When developers talk of mainline or upstream, they generally mean the latest unstable, not what was the unstable a month ago.
This hikey-mainline-rebase is worthless to me and anyone else trying to develop kernel code because we are working against 4.4.
It would be potentially useful if the the rebase branch were updated as soon as possible after X.YY-rc1 is released.
Tracking X.YY-rc2 through X.YY-rc7 is helpful but much less critical since it should be fairly easy for other developers to rebase between members of the X.YY family when they need to.
Working on top of rebase kernels is clearly still second best to working on the mainline but, nevertheless, when the hardware has compelling advantages it is much more comfortable if the focus of the rebase tree is -rc1.
Agreed. IMO, -rc1 and -rc2 bring in the big changes. So updating quickly up to -rc2 is helpful. There is also the hope the the stack of patches being rebased is getting reduced as we go.