From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Enable HIBERNATION in defconfig
Date: Sun, 2 Oct 2016 22:19:17 -0700 [thread overview]
Message-ID: <20161003051917.GC4403@localhost> (raw)
In-Reply-To: <20160915100231.GG2492@e104818-lin.cambridge.arm.com>
Hi,
On Thu, Sep 15, 2016 at 11:02:31AM +0100, Catalin Marinas wrote:
> On Thu, Sep 15, 2016 at 10:42:14AM +0100, Catalin Marinas wrote:
> > This patch adds CONFIG_HIBERNATION to the arm64 defconfig.
> >
> > Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> > ---
> > arch/arm64/configs/defconfig | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> > index eadf4855ad2d..91a7592029e3 100644
> > --- a/arch/arm64/configs/defconfig
> > +++ b/arch/arm64/configs/defconfig
> > @@ -80,6 +80,7 @@ CONFIG_KEXEC=y
> > # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
> > CONFIG_COMPAT=y
> > CONFIG_CPU_IDLE=y
> > +CONFIG_HIBERNATION=y
> > CONFIG_ARM_CPUIDLE=y
> > CONFIG_CPU_FREQ=y
> > CONFIG_ARM_BIG_LITTLE_CPUFREQ=y
>
> Or maybe it could go through arm-soc as it seems Arnd has picked up a
> few other defconfig patches.
When we just get a cc of a reply to a patch, it's usually pretty error prone
whether we end up applying it. Which happened here, I just came across this
when making a final sweep.
Yes, in general we tend to have more changes to the defconfig, so it's
appreciated to get these sent our way.
Given timing, resend after -rc1? We should be OK with applying it for 4.9
still around that time.
-Olof
next prev parent reply other threads:[~2016-10-03 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 9:42 [PATCH] arm64: Enable HIBERNATION in defconfig Catalin Marinas
2016-09-15 10:02 ` Catalin Marinas
2016-10-03 5:19 ` Olof Johansson [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-19 16:59 Catalin Marinas
2016-10-28 0:01 ` Olof Johansson
2016-08-26 15:28 Catalin Marinas
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=20161003051917.GC4403@localhost \
--to=olof@lixom.net \
--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).