Nicolas Pitre wrote:

> Indeed.  And that's exactly what I'm looking for in order to produce the 
> linaro-next kernel tree.  The linaro-next tree is discarded and rebuilt 
> from scratch by merging together a bunch of development trees on a 
> regular basis.  I'd like to add your up-to-date tree to the lot.

We currently don't have anything like a git,
what we have is this patchstack against Rothwells next-tags:
http://userweb.kernel.org/~linusw/st-ericsson/

This consists of the patches we have considered to be
in such a good shape that we have sent them off to the
different mailing lists and subsystem maintainers.

NB: this is on top of the stuff we already have pending
in next, which is currently actually a lot.

Right now we have ~49 patches pending in the latest next tag
and ~27 patches in the additional patch stack (i.e. stuff
under review).

I'm rebasing this patch stack agains Rothwells tree at irregular
intervals.

The reason for not having this in a git is that since we're
currently messing in so many subsystems and extending and
fixing the subsystems as we go along and since we get so many
cross-dependencies between subsystems, I have found it a
lot easier to just keep a simple patch stack for the time
being.

Maybe I'm just not understanding some easy way out of cross-
subsystem dependencies, but the way I'm experiencing it is
that we have done the simple drivers already, the stuff we
have left is all of the type where we must have some special
header file for the driver platform data creating a cross-
subsystem dependency to the ARM tree. Any incremental
fixes once the driver is in are usually a breeze to merge
and maintain.

We are making this even more elaborate by trying to push
stuff like DMA into drivers/dma/* and GPIO expanders into
drivers/gpio/* instead of just slamming all hairy cases
into arch/arm/* like many platforms have done previously...

Any hints on how to get out of this and create a simple
git tree or set of trees is welcome, I have yet not found
any.

Yours,
Linus Walleij

_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Reply via email to