linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM Based SoC Fixes for v4.6
Date: Thu, 28 Apr 2016 09:06:57 +1000	[thread overview]
Message-ID: <cover.1461798058.git.horms+renesas@verge.net.au> (raw)

Hi Olof, Hi Kevin, Hi Arnd,

Please consider these second round of Renesas ARM based SoC fixes for v4.6.

This fix allows serial to work on r8a7795-based boards where the optional
scif clock is not populated.

This pull request is based on the previous round of
such requests, tagged as renesas-fixes-for-v4.6,
which I have already sent a pull-request for.


The following changes since commit c531fb27e9699eaee478ee5686a3cca5dee73602:

  ARM: shmobile: timer: Fix preset_lpj leading to too short delays (2016-04-20 08:52:55 +1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-fixes2-for-v4.6

for you to fetch changes up to f5515f9cdff136dc32517d4b81fe2b9091237b4a:

  arm64: dts: r8a7795: Don't disable referenced optional scif clock (2016-04-26 09:44:48 +1000)

----------------------------------------------------------------
Second Round of Renesas ARM Based SoC Fixes for v4.6

* Don't disable referenced optional scif clock

----------------------------------------------------------------
Geert Uytterhoeven (1):
      arm64: dts: r8a7795: Don't disable referenced optional scif clock

 arch/arm64/boot/dts/renesas/r8a7795.dtsi | 1 -
 1 file changed, 1 deletion(-)

             reply	other threads:[~2016-04-27 23:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 23:06 Simon Horman [this message]
2016-04-27 23:07 ` [PATCH] arm64: dts: r8a7795: Don't disable referenced optional scif clock Simon Horman
2016-04-28 15:46 ` [GIT PULL] Second Round of Renesas ARM Based SoC Fixes for v4.6 Arnd Bergmann

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=cover.1461798058.git.horms+renesas@verge.net.au \
    --to=horms+renesas@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).