public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] clk: mvebu: changes for v3.16
Date: Tue, 13 May 2014 16:27:37 -0700	[thread overview]
Message-ID: <20140513232737.5943.78044@quantum> (raw)
In-Reply-To: <20140508145703.GC12708@titan.lakedaemon.net>

Quoting Jason Cooper (2014-05-08 07:57:03)
> Mike,
> 
> Here are the mvebu clock changes this time around.  Pretty easy, just
> one brand new driver.  This has been in -next for a while and is part of
> the awesome series by Thomas converting the legacy orion5x platform to
> devicetree.
> 
> Please pull.

Taken into clk-next.

Regards,
Mike

> 
> thx,
> 
> Jason.
> 
> 
> The following changes since commit c9eaa447e77efe77b7fa4c953bd62de8297fd6c5:
> 
>   Linux 3.15-rc1 (2014-04-13 14:18:35 -0700)
> 
> are available in the git repository at:
> 
>   git://git.infradead.org/linux-mvebu.git tags/clk-mvebu-3.16
> 
> for you to fetch changes up to 66ecbfea762ad28bd108db76775483b491068b92:
> 
>   clk: mvebu: add Orion5x clock driver (2014-04-26 01:03:55 +0000)
> 
> ----------------------------------------------------------------
> clk mvebu changes for v3.16
> 
>  - orion5x: brand new driver
> 
> ----------------------------------------------------------------
> Thomas Petazzoni (1):
>       clk: mvebu: add Orion5x clock driver
> 
>  .../devicetree/bindings/clock/mvebu-core-clock.txt |   8 +
>  drivers/clk/mvebu/Kconfig                          |   4 +
>  drivers/clk/mvebu/Makefile                         |   1 +
>  drivers/clk/mvebu/orion.c                          | 210 +++++++++++++++++++++
>  4 files changed, 223 insertions(+)
>  create mode 100644 drivers/clk/mvebu/orion.c

      reply	other threads:[~2014-05-13 23:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 14:57 [GIT PULL] clk: mvebu: changes for v3.16 Jason Cooper
2014-05-13 23:27 ` Mike Turquette [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140513232737.5943.78044@quantum \
    --to=mturquette@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox