From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Andi Kleen <ak@suse.de>, LKML <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: [linux-pm] Re: [Resend][PATCH] PM: Fix dependencies of CONFIG_SUSPEND and CONFIG_HIBERNATION (updated)
Date: Mon, 6 Aug 2007 13:56:22 +0200 [thread overview]
Message-ID: <200708061356.23030.rjw@sisk.pl> (raw)
In-Reply-To: <20070806113644.GA1790@elf.ucw.cz>
On Monday, 6 August 2007 13:36, Pavel Machek wrote:
> On Mon 2007-08-06 13:15:17, Johannes Berg wrote:
> > On Mon, 2007-08-06 at 12:26 +0200, Pavel Machek wrote:
> >
> > > Well, so that it does not bitrot? This is few bytes, I'd say, and I
> > > believe we have too many config options already.
> >
> > This is not an option the user is ever going to see. I think I'd
> > prefer
>
> Ok, option that users can't set is probably not evil.
>
> > having two new per-ARCH config symbols though:
> > config SUSPEND_UP_POSSIBLE
> > depends on ARCH_SUSPEND_UP_POSSIBLE
> >
> > and then the architecture gets to define that when it can suspend.
>
> Looks like a plan.
Hmm, why don't we do the $subject change first (the advantage if it is that
the patch is ready) and then move the necessary definitions to the arch level?
Greetings,
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
next prev parent reply other threads:[~2007-08-06 11:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 17:06 [Resend][PATCH] PM: Fix dependencies of CONFIG_SUSPEND and CONFIG_HIBERNATION (updated) Rafael J. Wysocki
2007-08-06 9:07 ` Pavel Machek
2007-08-06 9:07 ` Pavel Machek
2007-08-06 9:29 ` [linux-pm] " Johannes Berg
2007-08-06 10:26 ` Pavel Machek
2007-08-06 11:15 ` Johannes Berg
2007-08-06 11:15 ` [linux-pm] " Johannes Berg
2007-08-06 11:22 ` Johannes Berg
2007-08-06 11:22 ` [linux-pm] " Johannes Berg
2007-08-06 11:36 ` Pavel Machek
2007-08-06 11:36 ` [linux-pm] " Pavel Machek
2007-08-06 11:56 ` Rafael J. Wysocki
2007-08-06 11:56 ` Rafael J. Wysocki [this message]
2007-08-07 9:42 ` Johannes Berg
2007-08-07 9:42 ` [linux-pm] " Johannes Berg
2007-08-06 10:26 ` Pavel Machek
2007-08-06 11:14 ` [linux-pm] " Rafael J. Wysocki
2007-08-06 11:14 ` Rafael J. Wysocki
2007-08-06 9:29 ` Johannes Berg
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=200708061356.23030.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@linux-foundation.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.