From: Dennis Clarke <dclarke@blastwave.org>
To: linux-kernel@vger.kernel.org
Subject: arch/x86/platform/olpc/olpc-xo1-pm.c:159: undefined reference to `mfd_cell_disable'
Date: Fri, 4 Jan 2019 18:13:14 -0500 [thread overview]
Message-ID: <eaa688b4-b976-bd8c-01e0-0e5e43ee657c@blastwave.org> (raw)
In 4.19.13 I was surprised to see :
ld: arch/x86/platform/olpc/olpc-xo1-pm.o: in function `xo1_pm_remove':
/usr/local/build/linux_kernel/linux-4.19.13_20190102221644/arch/x86/platform/olpc/olpc-xo1-pm.c:159:
undefined reference to `mfd_cell_disable'
ld: arch/x86/platform/olpc/olpc-xo1-pm.o: in function `xo1_pm_probe':
/usr/local/build/linux_kernel/linux-4.19.13_20190102221644/arch/x86/platform/olpc/olpc-xo1-pm.c:133:
undefined reference to `mfd_cell_enable'
gmake: *** [Makefile:1032: vmlinux] Error 1
Command exited with non-zero status 2
Which seems to be defined in drivers/mfd/mfd-core.c :
https://github.com/torvalds/linux/blob/6f0d349d922ba44e4348a17a78ea51b7135965b1/drivers/mfd/mfd-core.c
Seems odd given that #include <linux/mfd/core.h> is in both
arch/x86/platform/olpc/olpc-xo1-pm.c and also
arch/x86/platform/olpc/olpc-xo1-sci.c and not sure where the issue is
however I have seen this twice
now. I'll hunt around and see if I can find where the issue is.
Dennis Clarke
reply other threads:[~2019-01-04 23:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=eaa688b4-b976-bd8c-01e0-0e5e43ee657c@blastwave.org \
--to=dclarke@blastwave.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®