From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/3] ARM: shmobile: Add Core-Standby-state for Suspend to RAM
Date: Fri, 30 May 2014 06:52:47 +0000 [thread overview]
Message-ID: <20140530065244.GA19611@verge.net.au> (raw)
In-Reply-To: <5386E089.3050003@renesas.com>
On Fri, May 30, 2014 at 03:21:19PM +0900, Magnus Damm wrote:
> On Fri, May 30, 2014 at 8:38 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Thu, May 29, 2014 at 04:23:53PM +0900, keita kobayashi wrote:
> >> These patches add Core-Standby-state for Suspend to RAM support to the
> >> r8a7790/r8a7791 SoC. This patch series depend on previously posted patch.
> >> [PATCH] ARM: shmobile: r8a7791: SYSC setup code.
> >>
> >> This patch series is based on renesas-devel-v3.15-rc7-20140526 tag
> >
> > Thanks.
> >
> > Please repost this series once that patch has been accepted
> > (I believe you need to post v2 of it to address some review of it.)
> >
> >> Keita Kobayashi (3):
> >> ARM: shmobile: APMU: Add Core-Standby-state for Suspend to RAM
> >> ARM: shmobile: r8a7790: Support Core-Standby for Suspend to RAM
> >> ARM: shmobile: r8a7791: Support Core-Standby for Suspend to RAM
>
> Hi Simon and Kobayashi-san,
>
> >From my point of view this series looks quite fine. I believe it
> should apply as-is on top of v2 of "[PATCH] ARM: shmobile: r8a7791:
> SYSC setup code", but I may fail to see some of the dependencies.
>
> Acked-by: Magnus Damm <damm+renesas@opensource.se>
>
> Kobayashi-san, please follow the guidance from Simon. I believe he
> will tell you if you need to resend or not.
>
> Simon, can you let us know how to proceed?
Thanks for the Acks.
I will queue up these patches.
next prev parent reply other threads:[~2014-05-30 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 7:23 [PATCH 0/3] ARM: shmobile: Add Core-Standby-state for Suspend to RAM keita kobayashi
2014-05-29 23:38 ` Simon Horman
2014-05-30 6:21 ` Magnus Damm
2014-05-30 6:52 ` Simon Horman [this message]
2014-05-30 7:36 ` Simon Horman
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=20140530065244.GA19611@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.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).