From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Rafael J. Wysocki" <rjw@sisk•pl>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: suspend tree build failure
Date: Mon, 17 Aug 2009 18:40:48 +1000 [thread overview]
Message-ID: <20090817184048.db6d94f9.sfr@canb.auug.org.au> (raw)
[Sorry if some get this twice, I fixed up the subject.]
Hi Rafael,
Today's linux-next build (powerpc allyesconfig) failed like this:
drivers/base/power/runtime.c:948: error: __ksymtab_pm_runtime_disable causes a section type conflict
Caused by commit d9d4cc5169ca18df9ff5afd31c6e6b715ecb454a ("PM: Introduce
core framework for run-time PM of I/O devices (rev. 17)") from the
suspend tree. This commit EXPORTs pm_runtime_disable which is an inline
function that calls __pm_runtime_disable (which is probably what was
meant to be EXPORTed).
I wish we could get these type of errors to fail on x86 as well ...
I have applied the following patch for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Mon, 17 Aug 2009 18:34:28 +1000
Subject: [PATCH] suspend: EXPORT the correct function.
Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
drivers/base/power/runtime.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/base/power/runtime.c b/drivers/base/power/runtime.c
index 28a3f91..38556f6 100644
--- a/drivers/base/power/runtime.c
+++ b/drivers/base/power/runtime.c
@@ -945,7 +945,7 @@ void __pm_runtime_disable(struct device *dev, bool check_resume)
out:
spin_unlock_irq(&dev->power.lock);
}
-EXPORT_SYMBOL_GPL(pm_runtime_disable);
+EXPORT_SYMBOL_GPL(__pm_runtime_disable);
/**
* pm_runtime_enable - Enable run-time PM of a device.
--
1.6.3.3
next reply other threads:[~2009-08-17 8:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 8:40 Stephen Rothwell [this message]
2009-08-17 12:06 ` linux-next: suspend tree build failure Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2009-10-12 3:00 Stephen Rothwell
2009-10-12 22:44 ` Rafael J. Wysocki
2009-10-13 0:58 ` Stephen Rothwell
2009-10-08 4:30 Stephen Rothwell
2009-10-06 2:55 Stephen Rothwell
2009-10-06 22:31 ` Rafael J. Wysocki
2009-10-07 4:29 ` Stephen Rothwell
2009-10-07 20:41 ` Rafael J. Wysocki
2009-10-07 23:48 ` Stephen Rothwell
2009-10-05 5:00 Stephen Rothwell
2009-10-05 23:55 ` Rafael J. Wysocki
2009-10-06 2:39 ` Stephen Rothwell
2009-08-18 8:30 Stephen Rothwell
2009-08-18 21:43 ` Rafael J. Wysocki
2009-08-18 22:13 ` Paul Mundt
2009-08-18 22:40 ` Rafael J. Wysocki
2009-08-18 22:47 ` Paul Mundt
2009-08-18 23:57 ` Stephen Rothwell
2009-03-16 9:13 Stephen Rothwell
2009-03-16 22:07 ` Rafael J. Wysocki
2009-03-16 23:09 ` Stephen Rothwell
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=20090817184048.db6d94f9.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rjw@sisk$(echo .)pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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