[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
On Tue, May 01, 2012 at 06:56:50PM -0700, Mike Turquette wrote: > On 20120501-19:19, Mark Brown wrote: > > To be honest it doesn't look like your patch is a particular issue here > > - there's wider process problems, for example we've managed to go > > through most of the release cycle and so far the only changes showing up > > in -next are: > I think that "wider process problems" is probably a euphemism, and I'll > take responsibility for that. This has been a learning process for me > and I underestimated the percentage of my time that would be consumed by > common clk maintenance. I'm trying to rectify that problem now. It's not really a euphamism - it really does seem like we've got all the technical stuff proceeding reasonably well but we're just struggling with the mechanics of actually getting the code into -next and on its way to mainline. > I was happy to push my changes to Linus directly (as discussed in > previous mails) but I'm starting to think that maybe having Arnd absorb > the clk-next branch as part of arm-soc would be the fastest way to > assist platforms that are porting over. > Do the platform folks agree? Is this suggestion sane? Seems to make sense to me; if there's some bits that are less clear you could always keep them on a branch separate to the one that the platforms use. It's probably also worth getting things into -next directly, that way integration testing of bleeding edge stuff can happen before it's been merged into other trees and it's hard to change. What I've tried do with regmap when it's been possible (it's not this time around because the stride changes touch everything) is to have topic branches so that people can pull in only the specific bits they need. I still end upn sending a pull request to Linus even if chunks of it have also gone via other trees.
Description: Digital signature