From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM list <linux-pm@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Len Brown <len.brown@intel.com>
Subject: Re: [PATCH 1/2] PM / sleep: Make suspend-to-idle-specific code depend on CONFIG_SUSPEND
Date: Tue, 19 May 2015 16:36:29 +0200 [thread overview]
Message-ID: <555B4A6D.1050001@linaro.org> (raw)
In-Reply-To: <2270439.0UMhzsTGM1@vostro.rjw.lan>
On 05/16/2015 01:38 AM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Since idle_should_freeze() is defined to always return 'false'
> for CONFIG_SUSPEND unset, all of the code depending on it in
> cpuidle_idle_call() is not necessary in that case.
>
> Make that code depend on CONFIG_SUSPEND too to avoid building it
> when it is not going to be used.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2015-05-19 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 23:37 [PATCH 0/2] PM: Avoid building suspend-to-idle code when it is not necessary Rafael J. Wysocki
2015-05-15 23:38 ` [PATCH 1/2] PM / sleep: Make suspend-to-idle-specific code depend on CONFIG_SUSPEND Rafael J. Wysocki
2015-05-18 14:49 ` Thomas Gleixner
2015-05-18 21:50 ` Rafael J. Wysocki
2015-05-19 14:36 ` Daniel Lezcano [this message]
2015-05-15 23:38 ` [PATCH 2/2] PM / sleep: Make ->enter_freeze callbacks " Rafael J. Wysocki
2015-05-18 12:18 ` Peter Zijlstra
2015-05-18 21:45 ` Rafael J. Wysocki
2015-05-19 15:00 ` Peter Zijlstra
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=555B4A6D.1050001@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.