public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-pm@lists.linux-foundation.org,
	Russell King <rmk@arm.linux.org.uk>
Subject: Re: + rework-pm_ops-pm_disk_mode-kill-misuse.patch	added to -mm tree
Date: Thu, 22 Mar 2007 16:28:24 +0100	[thread overview]
Message-ID: <1174577304.3588.17.camel@johannes.berg> (raw)
In-Reply-To: <acd2a5930703220823m3697cd98i47c3ead8e9fd19bb@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 757 bytes --]

On Thu, 2007-03-22 at 18:23 +0300, Vitaly Wool wrote:
> On 3/22/07, Johannes Berg <johannes@sipsolutions.net> wrote:
> > If you have a platform that doesn't allow CONFIG_SOFTWARE_SUSPEND (which
> > is only suspend to disk) and doesn't have pm_ops either, then you end up
> > with an empty /sys/power/state file.
> 
> CONFIG_SOFTWARE_SUSPEND is a misleading name then.

Oh, I don't disagree, but the help text for it makes it amply clear:

config SOFTWARE_SUSPEND
[...]
          Enable the suspend to disk (STD) functionality.

          You can suspend your machine with 'echo disk > /sys/power/state'.
          Alternatively, you can use the additional userland tools available
          from <http://suspend.sf.net>.
[...]

johannes

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2007-03-22 15:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 23:34 + rework-pm_ops-pm_disk_mode-kill-misuse.patch added to -mm tree akpm
2007-03-22  9:48 ` Russell King
2007-03-22  9:56   ` Andrew Morton
2007-03-22 10:03     ` Pavel Machek
2007-03-22 10:08       ` Johannes Berg
2007-03-22 13:26         ` Russell King
2007-03-22 13:31           ` Pavel Machek
2007-03-22 13:41             ` Vitaly Wool
2007-03-22 14:03               ` Pavel Machek
2007-03-22 14:27                 ` Vitaly Wool
2007-03-22 14:33                   ` Pavel Machek
2007-03-22 15:23                   ` Johannes Berg
2007-03-22 15:26                     ` Vitaly Wool
2007-03-22 14:24             ` Paul Mundt
2007-03-22 14:33               ` Pavel Machek
2007-03-22 14:35                 ` Paul Mundt
2007-03-22 17:36                   ` Andrew Morton
2007-03-22 17:51                     ` Johannes Berg
2007-03-22 15:05               ` Johannes Berg
2007-03-22 15:23                 ` Vitaly Wool
2007-03-22 15:28                   ` Johannes Berg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-03-22 18:00 akpm
2007-04-27 22:11 ` Johannes Berg
2007-04-27 22:55   ` Andrew Morton
2007-04-28  6:40     ` 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=1174577304.3588.17.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@ucw.cz \
    --cc=rmk@arm.linux.org.uk \
    --cc=vitalywool@gmail.com \
    /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