* Artem Bityutskiy <[email protected]> [091111 21:05]: > On Wed, 2009-11-11 at 10:42 -0800, Tony Lindgren wrote: > > * Tomi Valkeinen <[email protected]> [091111 01:43]: > > > On Wed, 2009-11-11 at 09:45 +0100, Valkeinen Tomi (Nokia-D/Helsinki) > > > wrote: > > > > On Tue, 2009-11-10 at 13:40 +0100, Artem Bityutskiy wrote: > > > > > Tomi, > > > > > > > > > > could you please kindly ask Stephen (CCed) to include the DSS2 tree > > > > > into > > > > > linux-next, because you are going to merge it the next merge window, > > > > > and > > > > > there does not seem to be any blocker for this. > > > > > > > > > > Being in linux-next for a while is really important. > > > > > > > > Stephen, would this be possible? DSS2 driver is rather big piece of > > > > code, even if it's quite isolated, so it would be nice to have it in > > > > linux-next. > > > > > > > > What does it require from me? A git tree, obviously, but what should it > > > > be based on? > > > > > > Ah, I just realized that DSS2 patches depend on patches from Tony's > > > tree. I guess I should base my tree on top of some Tony's tree that is > > > going to linux-next? > > > > Or I can merge them into my for-next if that's OK with everybody. This > > merge cycle is a pain for omap as we've moved all the common headers from > > include/mach to include/plat. > > I thought everything stable which you are going to merge next merge > window should be in the next branch by default. Especially these massive > re-names which potentially may break many things, right?
Yes, the renames are already there. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
