From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC R-Car SYSC Updates for v4.13
Date: Fri, 16 Jun 2017 15:31:08 +0200 [thread overview]
Message-ID: <cover.1497619041.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
Please consider these Renesas ARM based SoC R-Car SYSC updates for v4.13.
This has been separated out from the pull request
"[GIT PULL] Renesas ARM Based SoC Drivers Updates for v4.13"
due to differing dependencies. It seems cleanest to provide separate
branchs rather than do a merge to create a common base for a single branch.
The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-rcar-sysc-for-v4.13
for you to fetch changes up to 980532a5dda319eeafadc5c590376626ad178f4f:
soc: renesas: rcar-sysc: Use GENPD_FLAG_ALWAYS_ON (2017-06-15 21:10:41 +0200)
----------------------------------------------------------------
Renesas ARM Based SoC R-Car SYSC Updates for v4.13
Use GENPD_FLAG_ALWAYS_ON in R-Car SYSC driver
----------------------------------------------------------------
Geert Uytterhoeven (1):
soc: renesas: rcar-sysc: Use GENPD_FLAG_ALWAYS_ON
drivers/soc/renesas/rcar-sysc.c | 28 ++++------------------------
drivers/soc/renesas/rcar-sysc.h | 2 --
2 files changed, 4 insertions(+), 26 deletions(-)
next reply other threads:[~2017-06-16 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 13:31 Simon Horman [this message]
2017-06-16 13:31 ` [PATCH] soc: renesas: rcar-sysc: Use GENPD_FLAG_ALWAYS_ON Simon Horman
2017-06-19 5:51 ` [GIT PULL] Renesas ARM Based SoC R-Car SYSC Updates for v4.13 Olof Johansson
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.1497619041.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).