mbox

[GIT,PULL] clk: mvebu: for v3.14

Message ID 20131201170752.GT2879@titan.lakedaemon.net
State New
Headers show

Pull-request

git://git.infradead.org/linux-mvebu.git tags/mvebu-clk-3.14

Message

Jason Cooper Dec. 1, 2013, 5:07 p.m. UTC
Mike,

Here's the first round for v3.14.  These have been in -next for a week
now, without problem.

thx,

Jason.


The following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:

  Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)

are available in the git repository at:

  git://git.infradead.org/linux-mvebu.git tags/mvebu-clk-3.14

for you to fetch changes up to a2473b6c8279b95c5fa954f765da65cc27d6e2d2:

  clk: mvebu: Add Core Divider clock (2013-11-24 17:29:25 +0000)

----------------------------------------------------------------
mvebu clock changes for v3.14

 - mvebu: add the core divider clock driver
 - sparse cleanup

----------------------------------------------------------------
Ezequiel Garcia (1):
      clk: mvebu: Add Core Divider clock

Jisheng Zhang (1):
      clk: mvebu: staticize of_cpu_clk_setup

 drivers/clk/mvebu/Kconfig       |   5 +
 drivers/clk/mvebu/Makefile      |   1 +
 drivers/clk/mvebu/clk-corediv.c | 223 ++++++++++++++++++++++++++++++++++++++++
 drivers/clk/mvebu/clk-cpu.c     |   2 +-
 4 files changed, 230 insertions(+), 1 deletion(-)
 create mode 100644 drivers/clk/mvebu/clk-corediv.c

Comments

Jason Cooper Dec. 6, 2013, 4:26 p.m. UTC | #1
On Sun, Dec 01, 2013 at 12:07:52PM -0500, Jason Cooper wrote:
> Mike,
> 
> Here's the first round for v3.14.  These have been in -next for a week
> now, without problem.

Ping?  I see you've been pulling stuff into your -next branch.  Did you
miss this, or did I send it to the wrong list?

thx,

Jason.
Jason Cooper Dec. 11, 2013, 5:49 p.m. UTC | #2
On Fri, Dec 06, 2013 at 11:26:58AM -0500, Jason Cooper wrote:
> On Sun, Dec 01, 2013 at 12:07:52PM -0500, Jason Cooper wrote:
> > Mike,
> > 
> > Here's the first round for v3.14.  These have been in -next for a week
> > now, without problem.
> 
> Ping?  I see you've been pulling stuff into your -next branch.  Did you
> miss this, or did I send it to the wrong list?

re-ping?

thx,

Jason.
Ezequiel Garcia Dec. 20, 2013, 1:15 a.m. UTC | #3
On Wed, Dec 11, 2013 at 12:49:35PM -0500, Jason Cooper wrote:
> On Fri, Dec 06, 2013 at 11:26:58AM -0500, Jason Cooper wrote:
> > On Sun, Dec 01, 2013 at 12:07:52PM -0500, Jason Cooper wrote:
> > > Mike,
> > > 
> > > Here's the first round for v3.14.  These have been in -next for a week
> > > now, without problem.
> > 
> > Ping?  I see you've been pulling stuff into your -next branch.  Did you
> > miss this, or did I send it to the wrong list?
> 
> re-ping?
> 

Any news on this? Is there any problem with this driver?
Mike Turquette Dec. 20, 2013, 9:27 p.m. UTC | #4
Quoting Ezequiel Garcia (2013-12-19 17:15:22)
> On Wed, Dec 11, 2013 at 12:49:35PM -0500, Jason Cooper wrote:
> > On Fri, Dec 06, 2013 at 11:26:58AM -0500, Jason Cooper wrote:
> > > On Sun, Dec 01, 2013 at 12:07:52PM -0500, Jason Cooper wrote:
> > > > Mike,
> > > > 
> > > > Here's the first round for v3.14.  These have been in -next for a week
> > > > now, without problem.
> > > 
> > > Ping?  I see you've been pulling stuff into your -next branch.  Did you
> > > miss this, or did I send it to the wrong list?
> > 
> > re-ping?
> > 
> 
> Any news on this? Is there any problem with this driver?

Taken into clk-next.

Thanks!
Mike

> -- 
> Ezequiel GarcĂ­a, Free Electrons
> Embedded Linux, Kernel and Android Engineering
> http://free-electrons.com
Ezequiel Garcia Dec. 20, 2013, 9:35 p.m. UTC | #5
On Fri, Dec 20, 2013 at 01:27:33PM -0800, Mike Turquette wrote:
> Quoting Ezequiel Garcia (2013-12-19 17:15:22)
> > On Wed, Dec 11, 2013 at 12:49:35PM -0500, Jason Cooper wrote:
> > > On Fri, Dec 06, 2013 at 11:26:58AM -0500, Jason Cooper wrote:
> > > > On Sun, Dec 01, 2013 at 12:07:52PM -0500, Jason Cooper wrote:
> > > > > Mike,
> > > > > 
> > > > > Here's the first round for v3.14.  These have been in -next for a week
> > > > > now, without problem.
> > > > 
> > > > Ping?  I see you've been pulling stuff into your -next branch.  Did you
> > > > miss this, or did I send it to the wrong list?
> > > 
> > > re-ping?
> > > 
> > 
> > Any news on this? Is there any problem with this driver?
> 
> Taken into clk-next.
> 

Awesome!