mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Kill off legacy power management stuff.
Date: Fri, 13 Apr 2007 18:30:54 +1000	[thread overview]
Message-ID: <20070413183054.08ca0dff.sfr@canb.auug.org.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0704130416250.15118@CPE00045a9c397f-CM001225dbafb6>

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

On Fri, 13 Apr 2007 04:20:10 -0400 (EDT) "Robert P. J. Day" <rpjday@mindspring.com> wrote:
>
> On Fri, 13 Apr 2007, Stephen Rothwell wrote:
> >
> > One thing that comes to mind is that you will need some way to make sure
> > that only one of ACPI and APM get initialized ...
>
> i don't see how that has anything to do with removing legacy PM
> support.  you can select both ACPI and APM *now*.  if that's a bad
> thing, then fixing it is a completely independent issue.

Except your patch removes this hunk:

@@ -2264,14 +2248,6 @@ static int __init apm_init(void)
 		apm_info.disabled = 1;
 		return -ENODEV;
 	}
-	if (PM_IS_ACTIVE()) {
-		printk(KERN_NOTICE "apm: overridden by ACPI.\n");
-		apm_info.disabled = 1;
-		return -ENODEV;
-	}
-#ifdef CONFIG_PM_LEGACY
-	pm_active = 1;
-#endif

in apm.c and a similar piece of the ACPI initialisation that prevented
one initialising if the other had already initialised.

--
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-04-13  8:30 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 [this message]
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
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=20070413183054.08ca0dff.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.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

all inboxes | Powered by JetHome®