Thread (42 messages) 42 messages, 5 authors, 2012-05-03
STALE5159d
Revisions (4)
  1. v1 [diff vs current]
  2. v1 [diff vs current]
  3. v3 [diff vs current]
  4. v3 current

[PATCH V3 0/8] SPEAr: Move to common clock framework

From: Viresh Kumar <hidden>
Date: 2012-04-27 04:42:19

On 4/24/2012 12:20 PM, Viresh KUMAR wrote:
Mike,

You can apply all these patches as they don't have any dependency left (leaving
the ones included here) and will now apply cleanly over linux-next.
Mike,

These patches give compilation errors over your clk-next branch.
This happened due to following patch.

commit 1c0035d710dd3bfa86d58f851b8737c7f11a9bbc
Author: Shawn Guo [off-list ref]
Date:   Thu Apr 12 20:50:18 2012 +0800

    clk: pass parent_rate into .set_rate
    
    For most of .set_rate implementation, parent_rate will be used, so just
    like passing parent_rate into .recalc_rate, let's pass parent_rate into
    .set_rate too.
    
    It also updates the kernel doc for .set_rate ops.
    
    Signed-off-by: Shawn Guo [off-list ref]
    Signed-off-by: Mike Turquette [off-list ref]

I will send fixups as reply on individual patches, and then send you pull request
with these changes squashed to parent commits.

-- 
viresh
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help