From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Gautham R Shenoy <ego@in.ibm.com>, Ingo Molnar <mingo@elte.hu>,
Oleg Nesterov <oleg@tv-sign.ru>, Pavel Machek <pavel@ucw.cz>,
Pekka Enberg <penberg@cs.helsinki.fi>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -mm 1/2] Separate freezer from PM code
Date: Fri, 27 Apr 2007 13:20:18 -0700 [thread overview]
Message-ID: <46325B02.20106@goop.org> (raw)
In-Reply-To: <200704272220.57786.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> Makes sense. Please have a look at the updated patch below.
>
> Sam, does this one look better to you?
>
If freezer.c is in kernel/, then shouldn't the corresponding config var
be in a non-arch Kconfig file?
J
next prev parent reply other threads:[~2007-04-27 20:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 15:37 [PATCH -mm 0/2] Separate freezer from PM code Rafael J. Wysocki
2007-04-27 15:38 ` [PATCH -mm 1/2] " Rafael J. Wysocki
2007-04-27 16:15 ` Sam Ravnborg
2007-04-27 16:25 ` Jeremy Fitzhardinge
2007-04-27 20:20 ` Rafael J. Wysocki
2007-04-27 20:20 ` Jeremy Fitzhardinge [this message]
2007-04-27 21:29 ` Rafael J. Wysocki
2007-04-29 8:43 ` Sam Ravnborg
2007-04-27 15:40 ` [PATCH -mm 2/2] Introduce freezer flags Rafael J. Wysocki
2007-04-27 16:19 ` Sam Ravnborg
2007-04-27 16:33 ` Gautham R Shenoy
2007-04-27 21:40 ` Gautham R Shenoy
2007-04-27 21:49 ` Rafael J. Wysocki
2007-04-27 21:49 ` Gautham R Shenoy
2007-04-27 22:09 ` Rafael J. Wysocki
2007-04-27 22:07 ` Pavel Machek
2007-04-27 22:56 ` Rafael J. Wysocki
2007-04-28 7:07 ` Pavel Machek
2007-04-28 1:34 ` [PATCH -mm] Allow selective freezing of the system for different events Gautham R Shenoy
2007-04-28 6:22 ` Andrew Morton
2007-04-28 7:45 ` Gautham R Shenoy
2007-04-29 17:51 ` Rafael J. Wysocki
2007-04-30 19:19 ` Gautham R Shenoy
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=46325B02.20106@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=pavel@ucw.cz \
--cc=penberg@cs.helsinki.fi \
--cc=rjw@sisk.pl \
/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.