From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] qcom SoC changes for 4.4 *RESEND*
Date: Fri, 16 Oct 2015 09:56:30 -0700 [thread overview]
Message-ID: <56212C3E.8010603@codeaurora.org> (raw)
In-Reply-To: <5294153.vxTnuIq2gr@wuerfel>
On 10/15/2015 02:05 PM, Arnd Bergmann wrote:
>
> This also seemed like the right place
> to add a bugfix that I had in my queue:
>
> commit 73ebb85444b0472d90bb70a1a9e6b5df3f92c14c
> Author: Arnd Bergmann <arnd@arndb.de>
> Date: Tue Oct 13 17:05:39 2015 +0200
>
> soc: qcom/smem: add HWSPINLOCK dependency
>
> This fixes a build error when smem is enabled without hwspinlock:
>
> drivers/built-in.o: In function `qcom_smem_alloc':
> rockchip-efuse.c:(.text+0x7a3e4): undefined reference to `__hwspin_lock_timeout'
> rockchip-efuse.c:(.text+0x7a568): undefined reference to `__hwspin_unlock'
> drivers/built-in.o: In function `qcom_smem_remove':
> rockchip-efuse.c:(.text+0x7a5cc): undefined reference to `hwspin_lock_free'
> drivers/built-in.o: In function `qcom_smem_probe':
> rockchip-efuse.c:(.text+0x7a960): undefined reference to `hwspin_lock_request_specific'
> rockchip-efuse.c:(.text+0x7a988): undefined reference to `of_hwspin_lock_get_id'
> drivers/built-in.o: In function `qcom_smem_get':
> rockchip-efuse.c:(.text+0x7aa24): undefined reference to `__hwspin_lock_timeout'
> rockchip-efuse.c:(.text+0x7aafc): undefined reference to `__hwspin_unlock'
>
Can you share your .config? It looks like there are stubs for these, so
I'm lost how we got undefined references.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-10-16 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 22:10 [GIT PULL] qcom SoC changes for 4.4 *RESEND* Andy Gross
2015-10-15 21:05 ` Arnd Bergmann
2015-10-16 2:28 ` Andy Gross
2015-10-16 16:56 ` Stephen Boyd [this message]
2015-10-16 19:19 ` Arnd Bergmann
2015-10-16 20:04 ` Stephen Boyd
2015-10-16 20:17 ` Arnd Bergmann
2015-10-16 21:26 ` Stephen Boyd
2015-10-16 21:37 ` Arnd Bergmann
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=56212C3E.8010603@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).