From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Renesas ARM Based SoC Clock Fixes For v3.17
Date: Tue, 26 Aug 2014 09:09:29 +0000 [thread overview]
Message-ID: <20140826090929.GA1210@verge.net.au> (raw)
In-Reply-To: <cover.1408926048.git.horms+renesas@verge.net.au>
On Mon, Aug 25, 2014 at 10:09:47AM +0900, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM based SoC clock fixes for v3.17.
>
> This pull request is based on third round of Renesas ARM based SoC
> lock updates for v3.17, tagged as renesas-clock3-for-v3.17,
> which you have previously pulled.
>
> I would like the first to patches considered for -stable.
On reflection as these fixes do not fix any run-time problems
I would like to withdraw my request for them to considered for -stable.
I would, however, still like them considered for v3.17.
Thanks
> The following changes since commit a0f7e7496d56ac2da7c684e2035815318c17973a:
>
> ARM: shmobile: sh73a0: add CMT1 clock support for DT (2014-07-15 13:34:17 +0900)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-clock-fixes-for-v3.17
>
> for you to fetch changes up to 58b80ad6472c0fa12926dfa1f9103d3a326bdf18:
>
> ARM: shmobile: r8a7791: add missing 0x0100 for SDCKCR (2014-08-22 09:59:54 +0900)
>
> ----------------------------------------------------------------
> Renesas ARM Based SoC Clock Fixes For v3.17
>
> * ARM: shmobile: r8a7791: add missing 0x0100 for SDCKCR
>
> This resolves a problem introduced by 4bfb358b1d6cdeff
> ("ARM: shmobile: Add r8a7791 legacy SDHI clocks")
> which was included in v3.15.
>
> This fix does not have any run-time affect at this time.
>
> * ARM: shmobile: r8a7790: add missing 0x0100 for SDCKCR
>
> This resolves a problem introduced by 9f13ee6f83c52065
> ("ARM: shmobile: r8a7790: add div4 clocks")
> which was included in v3.11.
>
> This fix does not have any run-time affect at this time.
>
> * ARM: shmobile: sh73a0: Remove spurious 0x from SCIFB clock name
>
> This resolves a problem introduced by a0f7e7496d56ac2d
> ("ARM: shmobile: sh73a0: add CMT1 clock support for DT")
> which was included in v3.17-rc1.
>
> This fix does not have any run-time affect at this time as the clock in
> question is used by a SCIF device that is not enabled by default.
>
> ----------------------------------------------------------------
> Kuninori Morimoto (2):
> ARM: shmobile: r8a7790: add missing 0x0100 for SDCKCR
> ARM: shmobile: r8a7791: add missing 0x0100 for SDCKCR
>
> Simon Horman (1):
> ARM: shmobile: sh73a0: Remove spurious 0x from SCIFB clock name
>
> arch/arm/mach-shmobile/clock-r8a7790.c | 4 ++--
> arch/arm/mach-shmobile/clock-r8a7791.c | 2 +-
> arch/arm/mach-shmobile/clock-sh73a0.c | 2 +-
> 3 files changed, 4 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2014-08-26 9:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 1:09 [GIT PULL] Renesas ARM Based SoC Clock Fixes For v3.17 Simon Horman
2014-08-25 1:09 ` [PATCH 1/3] ARM: shmobile: sh73a0: Remove spurious 0x from SCIFB clock name Simon Horman
2014-08-25 1:09 ` [PATCH 2/3] ARM: shmobile: r8a7790: add missing 0x0100 for SDCKCR Simon Horman
2014-08-25 1:09 ` [PATCH 3/3] ARM: shmobile: r8a7791: " Simon Horman
2014-08-26 9:09 ` Simon Horman [this message]
2014-08-27 22:15 ` [GIT PULL] Renesas ARM Based SoC Clock Fixes For v3.17 Olof Johansson
2014-11-13 1:19 ` [GIT PULL] Renesas ARM Based SoC Clock Fixes for v3.18 Simon Horman
2014-11-13 1:19 ` [PATCH 1/3] ARM: shmobile: r8a7790: Fix SD3CKCR address Simon Horman
2014-11-13 1:19 ` [PATCH 2/3] ARM: shmobile: r8a7740 legacy: Add missing INTCA clock for irqpin module Simon Horman
2014-11-13 1:19 ` [PATCH 3/3] ARM: shmobile: r8a7740 legacy: Correct IIC0 parent clock Simon Horman
2014-11-19 21:20 ` [GIT PULL] Renesas ARM Based SoC Clock Fixes for v3.18 Arnd Bergmann
2014-11-20 0:22 ` Simon Horman
2014-11-20 8:56 ` Geert Uytterhoeven
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=20140826090929.GA1210@verge.net.au \
--to=horms@verge.net.au \
--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).