From: Randy Dunlap <randy.dunlap@oracle.com>
To: akuster <akuster@mvista.com>, linux-pm@lists.osdl.org
Cc: Andrew Morton <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] PM: fast power off - core
Date: Sun, 28 Jan 2007 10:09:42 -0800 [thread overview]
Message-ID: <20070128100942.edb5f7e1.randy.dunlap@oracle.com> (raw)
In-Reply-To: <45BBB097.1090207@mvista.com>
On Sat, 27 Jan 2007 10:05:43 -1000 akuster wrote:
> My apologies, I cc'd the wrong list the first time around.
{argh, attachments}
--- linux-2.6_dev.orig/kernel/power/Kconfig
+++ linux-2.6_dev/kernel/power/Kconfig
@@ -131,3 +131,5 @@ config SUSPEND_SMP
bool
depends on HOTPLUG_CPU && X86 && PM
default y
+
+source "kernel/power/fastoff/Kconfig"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Why a separate, new Kconfig file?
We shouldn't add a new Kconfig file for every new 1-2 kconfig symbols.
---
~Randy
next parent reply other threads:[~2007-01-28 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45BBB097.1090207@mvista.com>
2007-01-28 18:09 ` Randy Dunlap [this message]
2007-01-29 17:37 ` [PATCH 1/2] PM: fast power off - core akuster
2007-01-27 19:36 akuster
2007-01-27 20:08 ` Andrew Morton
2007-01-27 22:34 ` akuster
2007-01-28 19:12 ` Pavel Machek
2007-01-29 18:08 ` akuster
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=20070128100942.edb5f7e1.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=akuster@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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