From: "Mark Mason" <mason@broadcom.com>
To: linux-mips@linux-mips.org
Subject: [patch] power-down linkage fix
Date: Tue, 17 Jan 2006 12:04:07 -0800 [thread overview]
Message-ID: <20060117200407.GC19531@localhost.localdomain> (raw)
Hello,
The last git import created a dependency on pm_power_down. Borrowing from
ARM the following patch provides definitions of the needed variables in
order for kernels to link.
Please apply
/Mark
diff --git a/arch/mips/kernel/process.c b/arch/mips/kernel/process.c
--- a/arch/mips/kernel/process.c
+++ b/arch/mips/kernel/process.c
@@ -41,6 +41,15 @@
#include <asm/inst.h>
/*
+ * The following aren't currently used.
+ */
+void (*pm_idle)(void);
+EXPORT_SYMBOL(pm_idle);
+
+void (*pm_power_off)(void);
+EXPORT_SYMBOL(pm_power_off);
+
+/*
* The idle thread. There's no useful work to be done, so just try to conserve
* power and have a low exit latency (ie sit in a loop waiting for somebody to
* say that they'd like to reschedule)
next reply other threads:[~2006-01-17 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 20:04 Mark Mason [this message]
2006-01-19 0:50 ` [patch] power-down linkage fix Ralf Baechle
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=20060117200407.GC19531@localhost.localdomain \
--to=mason@broadcom.com \
--cc=linux-mips@linux-mips.org \
/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