From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, gregkh <greg@kroah.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH -next] driver core: syscore exports for modular APM
Date: Tue, 19 Apr 2011 08:35:46 -0700 [thread overview]
Message-ID: <20110419083546.e8981e49.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110419150641.644638d5.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
When CONFIG_APM=m, build fails with:
ERROR: "syscore_suspend" [arch/x86/kernel/apm.ko] undefined!
ERROR: "syscore_resume" [arch/x86/kernel/apm.ko] undefined!
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
drivers/base/syscore.c | 2 ++
1 file changed, 2 insertions(+)
--- linux-next-20110419.orig/drivers/base/syscore.c
+++ linux-next-20110419/drivers/base/syscore.c
@@ -73,6 +73,7 @@ int syscore_suspend(void)
return ret;
}
+EXPORT_SYMBOL_GPL(syscore_suspend);
/**
* syscore_resume - Execute all the registered system core resume callbacks.
@@ -95,6 +96,7 @@ void syscore_resume(void)
"Interrupts enabled after %pF\n", ops->resume);
}
}
+EXPORT_SYMBOL_GPL(syscore_resume);
#endif /* CONFIG_PM_SLEEP */
/**
next prev parent reply other threads:[~2011-04-19 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 5:06 linux-next: Tree for April 19 Stephen Rothwell
2011-04-19 15:35 ` Randy Dunlap [this message]
2011-04-19 21:17 ` [PATCH -next] driver core: syscore exports for modular APM Greg KH
2011-04-19 22:04 ` Rafael J. Wysocki
2011-04-20 20:39 ` Rafael J. Wysocki
2011-04-19 18:26 ` [PATCH -next] staging/intel_sst: intelmid needs delay.h Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2011-04-20 21:06 [PATCH -next] driver core: syscore exports for modular APM Randy Dunlap
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=20110419083546.e8981e49.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
--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;
as well as URLs for NNTP newsgroup(s).