linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dinh.linux@gmail.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] clk: socfpga: Clean-ups for 3.14
Date: Wed, 15 Jan 2014 06:24:06 -0600	[thread overview]
Message-ID: <52D67DE6.80908@gmail.com> (raw)
In-Reply-To: <20140115043206.4167.50892@quantum>


On 1/14/14 10:32 PM, Mike Turquette wrote:
> Quoting dinguyen at altera.com (2014-01-06 09:27:26)
>> Hi Mike,
>>
>> Please pull in these patches that cleans up the SOCFPGA clock driver. This is
>> V2 of the pull request that includes 4 patches from Steffen Trumtrar.
>>
>> Thanks,
>>
>> Dinh
>>
>> 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.rocketboards.org/linux-socfpga-next.git tags/socfpga-clk-for-3.14_v2
>>
>> for you to fetch changes up to d5387681665e58bafc1a9c745182f03aab0579c3:
>>
>>   clk: socfpga: split clk code (2014-01-06 11:22:22 -0600)
>>
>> ----------------------------------------------------------------
>> v2: SOCFPGA clk cleanups for 3.14
>>
>> ----------------------------------------------------------------
>> Dinh Nguyen (3):
>>       clk: socfpga: Map the clk manager base address in the clock driver
>>       clk: socfpga: Look for the GPIO_DB_CLK by its offset
> Hi Dinh,
>
> Patch "clk: socfpga: Look for the GPIO_DB_CLK by its offset" still
> causes a compilation error. I know it gets fixed by "clk: socfpga: fix
> compile error" later on but this still breaks git bisect.
>
> Can you please fold the fixes into the patches that introduce the bugs?
> No need to keep them separate since they are all part of the same pull
> request.

I have sent you a v3 of the pull request that folds in the fix. Thanks
for the
advice. I'll be sure to do that in the future.

Dinh
>
> Regards,
> Mike
>
>>       clk: socfpga: Remove socfpga_init_clocks
>>
>> Steffen Trumtrar (4):
>>       clk: socfpga: remove unused field
>>       clk: socfpga: fix define typo
>>       clk: socfpga: fix compile error
>>       clk: socfpga: split clk code
>>
>>  arch/arm/mach-socfpga/socfpga.c  |    5 -
>>  drivers/clk/socfpga/Makefile     |    3 +
>>  drivers/clk/socfpga/clk-gate.c   |  223 ++++++++++++++++++++++++++
>>  drivers/clk/socfpga/clk-periph.c |   94 +++++++++++
>>  drivers/clk/socfpga/clk-pll.c    |  111 +++++++++++++
>>  drivers/clk/socfpga/clk.c        |  328 ++------------------------------------
>>  drivers/clk/socfpga/clk.h        |   57 +++++++
>>  7 files changed, 500 insertions(+), 321 deletions(-)
>>  create mode 100644 drivers/clk/socfpga/clk-gate.c
>>  create mode 100644 drivers/clk/socfpga/clk-periph.c
>>  create mode 100644 drivers/clk/socfpga/clk-pll.c
>>  create mode 100644 drivers/clk/socfpga/clk.h
>>

  reply	other threads:[~2014-01-15 12:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 17:27 [GIT PULL] clk: socfpga: Clean-ups for 3.14 dinguyen at altera.com
2014-01-14  9:41 ` Dinh Nguyen
2014-01-15  4:32 ` Mike Turquette
2014-01-15 12:24   ` Dinh Nguyen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-13 23:07 dinguyen at altera.com
2013-12-29 19:05 ` Mike Turquette
2014-01-02 18:17   ` Dinh Nguyen

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=52D67DE6.80908@gmail.com \
    --to=dinh.linux@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).