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] Renesas ARM64 Based SoC SoC Updates for v4.6
Date: Fri, 26 Feb 2016 08:52:55 +0900	[thread overview]
Message-ID: <cover.1456442718.git.horms+renesas@verge.net.au> (raw)

Hi Olof, Hi Kevin, Hi Arnd,

Please consider these Renesas ARM64 based SoC SoC updates for v4.6.


The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:

  Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)

are available in the git repository at:

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

for you to fetch changes up to 2ee98234b88174f2bcafefb7918e2794a1fdbc98:

  arm64: renesas: Enable PM and PM_GENERIC_DOMAINS for SoCs with PM Domains (2016-02-19 14:55:18 +0900)

----------------------------------------------------------------
Renesas ARM64 Based SoC SoC Updates for v4.6

* Enable RENESAS_IRQC, and PM and PM_GENERIC_DOMAINS for SoCs with PM Domains

----------------------------------------------------------------
Geert Uytterhoeven (1):
      arm64: renesas: Enable PM and PM_GENERIC_DOMAINS for SoCs with PM Domains

Magnus Damm (1):
      arm64: renesas: Enable RENESAS_IRQC

 arch/arm64/Kconfig.platforms | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

             reply	other threads:[~2016-02-25 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 23:52 Simon Horman [this message]
2016-02-25 23:52 ` [PATCH 1/2] arm64: renesas: Enable RENESAS_IRQC Simon Horman
2016-02-25 23:52 ` [PATCH 2/2] arm64: renesas: Enable PM and PM_GENERIC_DOMAINS for SoCs with PM Domains Simon Horman
2016-02-29 15:19 ` [GIT PULL] Renesas ARM64 Based SoC SoC Updates 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.1456442718.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).