On Wed, 21 Mar 2012, Paul Walmsley wrote: > Hello Nico, > > On Tue, 20 Mar 2012, Nicolas Pitre wrote: > > > This common clk API has been under development for over *two* years > > already, with several attempts to merge it. And each previous merge > > attempt aborted because someone came along at the last minute to do > > exactly what you are doing i.e. underline all the flaws and call for a > > redesign. This is becoming a bad joke. > > There is a misunderstanding. I am not calling for a redesign. I am > simply stating that the current maturity level of the API and code should > be documented in the Kconfig dependencies or description text before the > code goes upstream. The objectives are to make future changes easier, set > expectations, and clearly disclose the extent to which the API and code > will need to change. Maybe there is no actual consensus on that extent. > > The code will be easier to change once it is in mainline, simply due to > > the fact that you can also change all its users at once. And it is well > > possible that most users won't have to deal with the same magnitude of > > complexity as yours, again reducing the scope for resistance to changes. > > I hope you are right. To me, these conclusions seem unlikely. It seems > equally likely that these rationales will make it much more difficult to > change the code once it's upstream and platforms are depending on it. No code should go upstream if no one depends on it. Therefore we change code that many platforms depend on all the time. What is killing us is the need to synchronize with multiple external code bases scattered around. > Particularly given the ongoing sensitivity to reducing "churn" of mainline > code, so publicly discussed. Please stop buying into that crap. We congratulate ourselves every merge cycles with the current process being able to deal with around half a million of lines changed every 3 months or so. It's pointless churn that is frowned upon, not useful and incremental API changes. I don't think that "pointless" would apply here. > So it seems like a good idea to attempt to address these potential > roadblocks and criticisms to major clock framework changes early. I understand your concern, however I don't think it is as serious as you are making it. > One last comment to address which is orthogonal to the technical content > of this discussion. > > > Otherwise one might ask where were you during those development years if > > you claim that the behavior and/or API of the common clock code still > > need to change significantly? > > One might ask this. If one were to ask this, another might briefly > outline the participation in public and private clock discussions at > Linaro Connect in Budapest and Redwood Shores, at LPC in Santa Rosa, at > ELCE/KS in Prague, at ELC in Redwood Shores, in conference calls, IRC > sessions, and private E-mails with many of the people included in the > header of this message, not to mention the list posts. Sure. I was there too and came across you many times. I just don't understand why some apparent consensus was built around the current submission, that people involved appeared to be highly satisfied at last, given the emphasis you are giving to your present concern which doesn't seem to be widely shared. This is a bit surprising. > None of the concerns that have been described are new. There has been an > endeavour to discuss them with anyone who seemed even remotely interested. Let's change tactics then. We've been discussing this code for over two years and no one could really benefit from it during that time. Maybe future discussion could become more productive and concrete when some code is merged _and_ used at last. Nicolas -- 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
