On Mon, 28 Jul 2008, Russell King - ARM Linux wrote: > On Mon, Jul 28, 2008 at 12:45:11PM +0100, Catalin Marinas wrote: > > ???I would really like some clear statement from you to know where > > to focus my attention (clean up the current patches even more or > > create separate arch/arm-t2). AFAICT, you don't really like these > > patches merged, in which case I'd have to focus on the second > > option. > > I've put my point of view forward in the responses to the patches. > I'm not sure what "clear statement" you're really after. For what my personal opinion is worth, simply considering a arch/arm-t2 solution should be completely out of the question. T2 support is possibly not too far from being somewhat tolerable given your latest patch series plus all suggestions to improve it further. So my biggest issue with this whole T2 unified assembly crap^H^H^H^Hsyntax has to do with the fact that it is apparently too late to change it. One of the best assets for the ARM architecture IMHO was its really neat assembly syntax and now it feels like ARM just screwed it. IMHO again, this was a big mistake from ARM Ltd not to consult people from the Open Source community who do write ARM assembly code when this unified syntax was elaborated. for one I certainly wasn't consulted at all. That could have provided ARM Ltd with inputs from folks whose first concern is long term code maintainability. Sure, many ARM Ltd partners just don't have such concern as they usually do write-once-and-forget assembly code and they're probably just happy with the current T2 syntax, or they simply don't care. This is not my case. In other words, and IMHO again, this whole new combined syntax just sucks. That is my personal statement and I don't know how to make it more clear. Now, since we're stuck with it for the foreseeable future, let's find a way to best accommodate it which does NOT include a separate architecture tree. Nicolas -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
