From: Ralf Baechle <ralf@linux-mips.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
David Howells <dhowells@redhat.com>
Subject: Re: pm_register() and pm_send_all()
Date: Thu, 13 Mar 2008 12:28:23 +0000 [thread overview]
Message-ID: <20080313122823.GA19415@linux-mips.org> (raw)
In-Reply-To: <20080313092813.GA24027@elf.ucw.cz>
On Thu, Mar 13, 2008 at 10:28:13AM +0100, Pavel Machek wrote:
> AFAICT pm_send_all is a nop when noone uses pm_register...
>
> Hmm.. can we just force CONFIG_PM_LEGACY=n, and see what happens?
>
> Or maybe this is better idea? It may break build somewhere, but it
> should be easy to fix... (it builds here, i386 and x86-64).
Looks correct to me, thus ACK.
Spinning that a little further I wonder how useful the rest of the
Alchemy code - which seems to only deal with devices - is. If at all.
I'm going to check with some Alchemy users if that code actually works or
can be removed. I think the latter. Also there is the APM emulation
available which provides similar functionality.
Ralf
next prev parent reply other threads:[~2008-03-13 12:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 22:00 pm_register() and pm_send_all() Andrew Morton
2008-03-12 22:54 ` Rafael J. Wysocki
2008-03-13 9:28 ` Pavel Machek
2008-03-13 12:28 ` Ralf Baechle [this message]
2008-03-13 14:19 ` Ralf Baechle
2008-03-13 18:06 ` Pavel Machek
2008-03-13 20:54 ` Rafael J. Wysocki
2008-03-13 21:04 ` Pavel Machek
2008-03-21 11:42 ` Ingo Molnar
2008-03-13 12:31 ` David Howells
2008-03-13 16:07 ` Andrew Morton
2008-03-13 18:05 ` Pavel Machek
2008-03-13 18:26 ` Andrew Morton
2008-03-14 8:04 ` 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=20080313122823.GA19415@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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.