From: Chris Metcalf <cmetcalf@tilera.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
kbuild test robot <fengguang.wu@intel.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: kernel/cgroup_freezer.c:151:3: error: 'system_freezing_cnt' undeclared
Date: Thu, 31 Jan 2013 21:23:08 -0500 [thread overview]
Message-ID: <510B270C.5000603@tilera.com> (raw)
In-Reply-To: <20130201005225.GQ6824@mtj.dyndns.org>
On 1/31/2013 7:52 PM, Tejun Heo wrote:
> Hello, Chris.
>
> On Thu, Jan 31, 2013 at 07:46:09PM -0500, Chris Metcalf wrote:
>> That seems reasonable to me, but I'm happy to experiment with
>> including Kconfig.freezer from the arch/tile/Kconfig if that feels
>> like a better solution.
> AFAICS, there's nothing arch specific about freezer and cgroup_freezer
> could be useful even without powersaving, so maybe give it a shot?
It builds with the following change. Look good to you?
commit 8c9632acfaea4cf6ae064d8291eea989b0df2bcf
Author: Chris Metcalf <cmetcalf@tilera.com>
Date: Thu Jan 31 21:21:36 2013 -0500
tile: include kernel/Kconfig.freezer in tile Kconfig
Signed-off-by: Chris Metcalf <cmetcalf@tilera.com>
diff --git a/arch/tile/Kconfig b/arch/tile/Kconfig
index 1adb853..d9072ba 100644
--- a/arch/tile/Kconfig
+++ b/arch/tile/Kconfig
@@ -142,6 +142,8 @@ config ARCH_DEFCONFIG
source "init/Kconfig"
+source "kernel/Kconfig.freezer"
+
menu "Tilera-specific configuration"
config NR_CPUS
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2013-02-01 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <510aa746.fVU8ZdQ2hys/RwjS%fengguang.wu@intel.com>
2013-01-31 23:14 ` kernel/cgroup_freezer.c:151:3: error: 'system_freezing_cnt' undeclared Tejun Heo
2013-02-01 0:46 ` Chris Metcalf
2013-02-01 0:52 ` Tejun Heo
2013-02-01 2:23 ` Chris Metcalf [this message]
2013-02-01 2:28 ` Tejun Heo
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=510B270C.5000603@tilera.com \
--to=cmetcalf@tilera.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tj@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 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.