On Fri, Apr 13, 2012 at 2:21 AM, Mark Brown
wrote:
> On Wed, Apr 11, 2012 at 06:02:38PM -0700, Mike Turquette wrote:
>> This series collects many of the fixes posted for the recently merged
>> common clock framework as well as some general clean-up. Most of the
>> code classifies as a clean-up mo
On Wed, Apr 11, 2012 at 06:02:38PM -0700, Mike Turquette wrote:
> This series collects many of the fixes posted for the recently merged
> common clock framework as well as some general clean-up. Most of the
> code classifies as a clean-up moreso than a bug fix; hopefully this is
> not a problem si
On Thu, Apr 12, 2012 at 11:14:38AM +, Arnd Bergmann wrote:
> On Thursday 12 April 2012, Mike Turquette wrote:
> > This series collects many of the fixes posted for the recently merged
> > common clock framework as well as some general clean-up. Most of the
> > code classifies as a clean-up mor
On Thursday 12 April 2012, Mike Turquette wrote:
> This series collects many of the fixes posted for the recently merged
> common clock framework as well as some general clean-up. Most of the
> code classifies as a clean-up moreso than a bug fix; hopefully this is
> not a problem since the common
On Wed, Apr 11, 2012 at 06:02:38PM -0700, Mike Turquette wrote:
> This series collects many of the fixes posted for the recently merged
> common clock framework as well as some general clean-up. Most of the
> code classifies as a clean-up moreso than a bug fix; hopefully this is
> not a problem si
This series collects many of the fixes posted for the recently merged
common clock framework as well as some general clean-up. Most of the
code classifies as a clean-up moreso than a bug fix; hopefully this is
not a problem since the common clk framework is new code pulled for 3.4.
Patches are ba
