All of lore.kernel.org
 help / color / mirror / Atom feed
From: dinguyen@altera.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] clk: socfpga: Clock fix for 3.13
Date: Mon, 2 Dec 2013 11:09:28 -0600	[thread overview]
Message-ID: <1386004168.11807.0.camel@linux-builds1> (raw)
In-Reply-To: <20131127204948.16819.21032@quantum>

On Wed, 2013-11-27 at 12:49 -0800, Mike Turquette wrote:
> Quoting Dinh Nguyen (2013-11-07 02:11:49)
> > Hi Mike,
> > 
> > On 10/24/13 3:41 AM, dinguyen at altera.com wrote:
> > > The following changes since commit 15c03dd4859ab16f9212238f29dd315654aa94f6:
> > >
> > >   Linux 3.12-rc3 (2013-09-29 15:02:38 -0700)
> > >
> > > are available in the git repository at:
> > >
> > >   git://git.rocketboards.org/linux-socfpga-next.git tags/socfpga-clk-for-3.13
> > >
> > > for you to fetch changes up to f592c5da6869133de941e44ef2ed4ede7f6b2791:
> > >
> > >   clk: socfpga: Remove check for "reg" property in socfpga_clk_init (2013-10-24 03:18:30 -0500)
> > >
> > > ----------------------------------------------------------------
> > > Clock fix for SOCFPGA
> > >
> > > Remove check for "reg" property in socfpga_clk_init() function
> > > This allows for clk property to be assigned for the arm_twd timer, which
> > > will lead to removing socfpga_init_clocks().
> > >
> > > ----------------------------------------------------------------
> > > Dinh Nguyen (1):
> > >       clk: socfpga: Remove check for "reg" property in socfpga_clk_init
> > >
> > >  drivers/clk/socfpga/clk.c |    4 +---
> > >  1 file changed, 1 insertion(+), 3 deletions(-)
> > >
> > Can you please pull this?
> 
> Taken into clk-next.

Thanks Mike.

Dinh
> 
> Thanks,
> Mike
> 
> > Thanks,
> > Dinh
> 

      reply	other threads:[~2013-12-02 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  8:41 [GIT PULL] clk: socfpga: Clock fix for 3.13 dinguyen at altera.com
2013-11-07 10:11 ` Dinh Nguyen
2013-11-27 20:49   ` Mike Turquette
2013-12-02 17:09     ` Dinh Nguyen [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=1386004168.11807.0.camel@linux-builds1 \
    --to=dinguyen@altera.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.