mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	pm list <linux-pm@lists.linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH][RFC] Kill off legacy power management stuff.
Date: Wed, 18 Apr 2007 14:31:33 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0704181427470.13500@localhost.localdomain> (raw)
In-Reply-To: <46265F60.4040600@tmr.com>

On Wed, 18 Apr 2007, Bill Davidsen wrote:

> Robert P. J. Day wrote:
...
> > um ... what does APM have to do with legacy PM?  two different
> > issues, no?

> Since the patches are going into apm.c and apm was used for suspend
> and poweroff before ACPI was a feature of the hardware, I assume
> there's a relationship. As of 2.6.9 ACPI still couldn't power down
> one of my old boxes, it hasn't been updated since that time, so I
> can't say what later kernels will do.

perhaps i completely misunderstood what i was looking at but when i
submitted a patch to remove "legacy power management," i wasn't
referring to APM.  i was talking about the PM stuff even *older* than
that, that's listed as "Legacy Power Management API (DEPRECATED)"
under the PM config menu.

so, politics and scheduling aside, was that earlier patch a reasonable
and correct way to do *that*?

rday

-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================

  reply	other threads:[~2007-04-18 18:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13  0:33 Robert P. J. Day
2007-04-13  8:09 ` Stephen Rothwell
2007-04-13  8:20   ` Robert P. J. Day
2007-04-13  8:30     ` Stephen Rothwell
2007-04-13  8:50       ` Robert P. J. Day
2007-04-14 12:22       ` {Spam?} " Robert P. J. Day
2007-04-14 13:01       ` Robert P. J. Day
2007-04-18 19:24         ` Len Brown
2007-04-18 20:23           ` Robert P. J. Day
2007-04-18 21:23             ` Len Brown
2007-04-18 23:45               ` Robert P. J. Day
2007-04-18 23:58               ` Dave Jones
2007-04-19  0:35                 ` Robert P. J. Day
2007-04-19 17:27                   ` Len Brown
2007-04-13  8:22 ` Rafael J. Wysocki
2007-04-13  9:51   ` [linux-pm] " David Brownell
2007-04-15 10:23   ` Pavel Machek
2007-04-17 22:12   ` Bill Davidsen
2007-04-17 22:28     ` [linux-pm] " David Brownell
2007-04-18  0:46     ` Robert P. J. Day
2007-04-18 18:11       ` Bill Davidsen
2007-04-18 18:31         ` Robert P. J. Day [this message]
2007-04-18 20:10         ` Pavel Machek

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=Pine.LNX.4.64.0704181427470.13500@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®