All of lore.kernel.org
 help / color / mirror / Atom feed
From: mturquette@ti.com (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] clk/mxs for 3.6 (part 2)
Date: Thu, 12 Jul 2012 09:51:45 -0700	[thread overview]
Message-ID: <20120712165145.GI2772@gmail.com> (raw)
In-Reply-To: <20120712074238.GK6971@S2101-09.ap.freescale.net>

On 20120712-15:42, Shawn Guo wrote:
> Hi Mike,
> 
> Here is one more clk/mxs patch (last one, I believe) for 3.6.
> Please pull.
> 

It's in clk-next now.

Regards,
Mike

> Regards,
> Shawn
> 
> The following changes since commit 64e2bc41304726a5ca8a4d37754db69b88841ebf:
> 
>   clk: mxs: imx28: decrease the frequency of ref_io1 for SSP2 and SSP3 (2012-07-05 09:36:44 +0800)
> 
> are available in the git repository at:
>   git://git.linaro.org/people/shawnguo/linux-2.6.git clk/mxs-for-3.6
> 
> Richard Zhao (1):
>       clk: mxs: clk_register_clkdev mx28 usb clocks
> 
>  drivers/clk/mxs/clk-imx28.c |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> 

      reply	other threads:[~2012-07-12 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12  7:42 [GIT PULL] clk/mxs for 3.6 (part 2) Shawn Guo
2012-07-12 16:51 ` 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=20120712165145.GI2772@gmail.com \
    --to=mturquette@ti.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.