Messages in this thread |  | | | Date | Thu, 14 Apr 2011 15:00:49 +0100 | | From | Mark Brown <> | | Subject | Re: [PATCH 0/2] Common struct clk implementation, v14 |
| |
On Thu, Apr 14, 2011 at 09:39:58AM -0400, Nicolas Pitre wrote: > On Thu, 14 Apr 2011, Russell King - ARM Linux wrote:
> > Adding it without anyone using it doesn't solve anything. We need > > people to commit to producing patches to use it for the next merge > > window.
> People are simply waiting for the API to hit some upstream tree (like > yours) before committing to it. You would be in a much better position > if those patches are in your tree, so that you can tell people: "Here's > the Git branch with the API in it, so now I'm expecting patches to > convert clock users to it".
One way of doing this would be to apply the patches to a branch in your tree which isn't merged into -next and request that architecture maintainers wishing to make use of the branch pull it into their trees. That way it'll go into -next with at least one user but multiple architectures can still work on using it in the initial merge.
|  |