From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Dave Jones <davej@redhat.com>
Cc: Len Brown <lenb@kernel.org>,
davej@codemonkey.org.uk, Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Kill off legacy power management stuff.
Date: Wed, 18 Apr 2007 20:35:22 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704182028320.5826@localhost.localdomain> (raw)
In-Reply-To: <20070418235806.GD20204@redhat.com>
On Wed, 18 Apr 2007, Dave Jones wrote:
> On Wed, Apr 18, 2007 at 05:23:15PM -0400, Len Brown wrote:
>
> > > p.p.s. patch improvements that will let me avoid doing any of that
> > > myself always welcome. :-)
> >
> > well, I'm sorry that I've known about the APM issue for a long time
> > and done nothing about it. I did ping davej when he broke it,
> > but his to-do list is probably even longer than mine.
>
> ping timeout.
>
> I don't recall too many of the details surrounding those changes,
> but I certainly won't stand in the way of anyone trying to fix it.
> It sounds like you and Robert are on top of it, or do you want me to
> poke at it ?
well, before i get even more confused by what was (once upon a time) a
fairly straightforward removal patch, the first obvious question is --
are there *any* circumstances that *require* a config selection of
CONFIG_PM_LEGACY, as opposed to a selection of APM and/or ACPI? if
there are, then it can't simply be removed. my original patch
submission was based on the assumption that absolutely no one needed
the legacy stuff anymore and absolutely everything related to it could
be scrapped.
so, first things first: what *needs* legacy PM at the moment?
rday
p.s. i'm confused by the header file include/linux/pm_legacy.h,
especially this part:
========================
#ifdef CONFIG_PM_LEGACY
...
# else /* CONFIG_PM_LEGACY */
#define PM_IS_ACTIVE() 0
...
#endif
=======================
so the macro "PM_IS_ACTIVE()" represents whether *legacy* PM has
been selected. in other words, it makes no (apparent) sense that the
value of that macro would represent some kind of contention mechanism
between APM and ACPI, which is entirely independent from the legacy
stuff. right?
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next prev parent reply other threads:[~2007-04-19 0:37 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 [this message]
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
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.0704182028320.5826@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=davej@codemonkey.org.uk \
--cc=davej@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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®