From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: shmobile: bockw: Do not disable SUSPEND in defconfig
Date: Fri, 22 Aug 2014 10:40:27 +0900 [thread overview]
Message-ID: <20140822014027.GA9099@verge.net.au> (raw)
In-Reply-To: <1408052188-8551-1-git-send-email-horms+renesas@verge.net.au>
On Fri, Aug 15, 2014 at 06:36:28AM +0900, Simon Horman wrote:
> As of "ARM: shmobile: r8a7778: Add missing call to shmobile_init_late()"
> suspend-to-ram is now supported on the r8a7778 SoC and thus the bockw
> board.
>
> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
I have queued this up.
> ---
> arch/arm/configs/bockw_defconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm/configs/bockw_defconfig b/arch/arm/configs/bockw_defconfig
> index 70b3f45..1dde5da 100644
> --- a/arch/arm/configs/bockw_defconfig
> +++ b/arch/arm/configs/bockw_defconfig
> @@ -29,7 +29,6 @@ CONFIG_ZBOOT_ROM_BSS=0x0
> CONFIG_ARM_APPENDED_DTB=y
> CONFIG_VFP=y
> # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
> -# CONFIG_SUSPEND is not set
> CONFIG_PM_RUNTIME=y
> CONFIG_NET=y
> CONFIG_PACKET=y
> --
> 2.0.1
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2014-08-22 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 21:36 [PATCH] ARM: shmobile: bockw: Do not disable SUSPEND in defconfig Simon Horman
2014-08-22 1:40 ` Simon Horman [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-25 1:09 [GIT PULL] Second Round Of Renesas ARM Based SoC Defconfig Updates For v3.18 Simon Horman
2014-08-25 1:10 ` [PATCH] ARM: shmobile: bockw: Do not disable SUSPEND in defconfig 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=20140822014027.GA9099@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).