On Friday 18 March 2011, Russell King - ARM Linux wrote: > I do get the impression that you're extremely unhappy with the way ARM > stuff works, and I've no real idea how to solve that. I think much of > it is down to perception rather than anything tangible. > > Maybe the only solution is for ARM to fork the kernel, which is something > I really don't want to do - but from what I'm seeing its the only solution > which could come close to making you happy. I'm still new to the ARM world, but I think one real problem is the way that all platforms have their own trees with a very flat hierarchy -- a lot of people directly ask Linus to pull their trees, and the main way to sort out conflicts is linux-next. The number of platforms in the ARM arch is still increasing, so I assume that this only gets worse. This would be no easier if everyone was asking you to pull their trees, as I believe was the case before that. The amount of code getting changed there is too large to get reviewed by a single person, and I believe neither of you really wants the burden to judge if all of the branches are ok (and complain to the authors when they are not). Russell, do you think it would help to have an additional ARM platform tree that collects all the changes that impact only the platform code but not the core architecture? I believe that would be a way out, but requires a careful selection of people responsible for it. In particular, I don't think a single person can handle it without good sub-maintainers. The way that x86 is maintained is to have a small group of people that all have write access to one tree, so patches and branches from downstream maintainers can get pulled by a number of people, when at least one of them in totally comfortable with the contents and nobody else objects. In case one of them is unhappy about something that went in, it can always get reverted and will not be applied again until everybody is happy with it. I think a similar setup would be possible for ARM, but only if you are in the team, plus one person from at least ARM Ltd (Catalin?), Linaro (Nicolas?) and maybe one or two more, but none of the actual SoC vendors that produce the bulk of the code that would go in there. It would also require buy-in from Linus eventually, to make it clear that he would pull from that tree directly and no longer from other subarchitecture trees, once the process has been proven to work for everyone. I don't think I would want to be on the committers team myself, to make it not too Linaro-heavy, but I can definitely offer a significant amount of time for reviewing patches to be committed by someone else. Also, I would assume that your own time would keep focused on the core ARM tree that already keeps you busy enough. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
