On Mon, Apr 16, 2012 at 6:46 PM, Shawn Guo shawn.guo@linaro.org wrote:
On 17 April 2012 07:10, Turquette, Mike mturquette@ti.com wrote: ...
Yes, this was a braindead change on my part. I'll remove the kstrdup in my next series (the rest of this patch will stay in).
Do you have an ETA on that? A few platform porting are waiting for a stable branch with all necessary fixup/cleanup integrated to publish the patches.
That is a good question. I think it is worth waiting on Saravana's patch which exposes non-private members of struct clk via struct clk_hw. This will have an effect on both platform clock data and code.
I do not think that there is a point in pushing another series out until I get that in since it will shake things up for platforms trying to convert over. And due to the invasive nature I'm still not sure if this stuff will go into an -rc or some -next branch for 3.5. I don't see the harm in keeping it in a -next branch for 3.5 where all platforms can base on that branch since they will be queuing up for 3.5 anyway.
Regards, Mike
Regards, Shawn