All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alexey Starikovskiy <aystarik@gmail.com>,
	Pavel Machek <pavel@ucw.cz>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Maciek Rutecki <maciej.rutecki@gmail.com>
Subject: Re: 2.6.23-rc6: S4 and S5 no longer listed as supported on Toshiba Satellite A40
Date: Thu, 20 Sep 2007 23:18:43 +0200	[thread overview]
Message-ID: <200709202318.44676.elendil@planet.nl> (raw)
In-Reply-To: <200709202232.33309.elendil@planet.nl>

On Thursday 20 September 2007, Frans Pop wrote:
> On Thursday 20 September 2007, Rafael J. Wysocki wrote:
> > On Thursday, 20 September 2007 20:33, Alexey Starikovskiy wrote:
> > > Frans Pop wrote:
> > > > Maybe S0 should be taken outside the #ifdef and the loop as that
> > > > state is also basically always there?
> > >
> > > Don't think it is worth the trouble. We already have this loop almost
> > > completely unrolled, let's not make it complete mess...
> >
> > Well, you could use "(supports S0" instead of just "(supports". ;-)
>
> After thinking about this a bit more, I think this does make sense for
> three (admittedly minor) reasons:
> - consistency between messages with and without CONFIG_SUSPEND
> - consistency with /proc/acpi/sleep
> - avoiding unnecessary change from previous versions.

One additional reason...

With current code, sleep_states(0) will not be set if compiled without 
CONFIG_SUSPEND, which means that S0 will also disappear from
/proc/acpi/sleep. With pre-2.6.23 code it would be listed there.

I think that is even a more relevant change than the display issue and could 
possibly even be considered a user-space interface regression.
My proposed patch fixes that too.

Note that the patch currently does not call acpi_get_sleep_type_data for S0, 
but (partially from Rafael's comment) I was assuming that for S0 that does 
not really matter. If it does, then the patch could easily be adjusted to 
include that.

      parent reply	other threads:[~2007-09-20 21:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 18:14 2.6.23-rc6: S4 and S5 no longer listed as supported on Toshiba Satellite A40 Frans Pop
2007-09-20 10:53 ` Pavel Machek
2007-09-20 12:37   ` Frans Pop
2007-09-20 16:01     ` Maciek Rutecki
2007-09-20 16:34       ` Alexey Starikovskiy
2007-09-20 20:01         ` Rafael J. Wysocki
2007-09-20 16:59       ` 2.6.23-rc6: S4 and S5 no longer listed as supported on ToshibaSatellite A40 Romano Giannetti
2007-09-20 16:59         ` Romano Giannetti
2007-09-20 16:33     ` 2.6.23-rc6: S4 and S5 no longer listed as supported on Toshiba Satellite A40 Frans Pop
2007-09-20 16:33     ` Maciek Rutecki
2007-09-20 17:29       ` Alexey Starikovskiy
2007-09-20 18:17         ` Frans Pop
2007-09-20 18:17           ` Frans Pop
2007-09-20 18:33           ` Alexey Starikovskiy
2007-09-20 20:07             ` Rafael J. Wysocki
2007-09-20 20:32               ` Frans Pop
2007-09-20 20:53                 ` Rafael J. Wysocki
2007-09-21 14:04                   ` Alexey Starikovskiy
2007-09-21 14:33                     ` Rafael J. Wysocki
2007-09-20 21:18                 ` Frans Pop [this message]

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=200709202318.44676.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=aystarik@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=pavel@ucw.cz \
    --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.