2013/6/11 Mark Brown <broonie@xxxxxxxxxx>: > On Tue, Jun 11, 2013 at 09:14:41AM +0800, Barry Song wrote: > >> the mainline idea you mentioned is that you don't care about any early >> device, which means some devices want to start earlier than others in >> some real automative user scenerioes. >> but i think another important idea is that mainline codes come from >> branches of different vendors and serve final users of those drivers, >> but not only make source codes no difference to all environments. the >> auto users i2c-sirf serves, here, actually means some differences with >> PC/tablet/mobilephone. we don't make codes good-looking by losing >> functionality and not close to final users. > > It's not that people don't care about these users, it's that people > don't care too much about out of tree users. Part of the goal here is > to convince people working on such applications that they should make > mainline better for everyone so that you don't need external code to > make the kernel useful. Mark, then this is really confusing me. for this reason, the target should be making this out-of-tree stuff be inside the tree. to make i2c-sirf "mainline better and not need external code", the target should be making this external code not external but become internal. otherwise, my mainline users will always need this external code. -barry -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
