public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Baolin Wang <baolin.wang@linaro•org>
Subject: linux-next: build failure after merge of the regmap tree
Date: Thu, 2 Nov 2017 11:57:12 +1100	[thread overview]
Message-ID: <20171102115712.231001ac@canb.auug.org.au> (raw)

Hi Mark,

After merging the regmap tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/base/regmap/regmap.o: In function `regmap_unlock_hwlock':
regmap.c:(.text+0x13a5): undefined reference to `__hwspin_unlock'
drivers/base/regmap/regmap.o: In function `regmap_unlock_hwlock_irq':
regmap.c:(.text+0x13d8): undefined reference to `__hwspin_unlock'
drivers/base/regmap/regmap.o: In function `regmap_unlock_hwlock_irqrestore':
regmap.c:(.text+0x140a): undefined reference to `__hwspin_unlock'
drivers/base/regmap/regmap.o: In function `regmap_lock_hwlock':
regmap.c:(.text+0x144a): undefined reference to `__hwspin_lock_timeout'
drivers/base/regmap/regmap.o: In function `regmap_lock_hwlock_irq':
regmap.c:(.text+0x148d): undefined reference to `__hwspin_lock_timeout'
drivers/base/regmap/regmap.o: In function `regmap_lock_hwlock_irqsave':
regmap.c:(.text+0x14cf): undefined reference to `__hwspin_lock_timeout'
drivers/base/regmap/regmap.o: In function `__regmap_init':
(.text+0x5139): undefined reference to `hwspin_lock_free'
drivers/base/regmap/regmap.o: In function `__regmap_init':
(.text+0x5e25): undefined reference to `hwspin_lock_request_specific'

Presumably caused by commit

  8698b9364710 ("regmap: Add hardware spinlock support")

Note that CONFIG_HWSPINLOCK=m for this build, but CONFIG_REGMAP=y

I have used the version of the regmap tree from next-20171018 for today.

-- 
Cheers,
Stephen Rothwell

next             reply	other threads:[~2017-11-02  0:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02  0:57 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-11-27  7:24 linux-next: build failure after merge of the regmap tree Stephen Rothwell
2020-11-30 17:59 ` Mark Brown
2020-11-30 18:07   ` Pierre-Louis Bossart
2020-11-30 18:11     ` Mark Brown
2020-11-30 18:21       ` Pierre-Louis Bossart
2012-04-11  4:13 Stephen Rothwell
2012-04-11  8:17 ` Mark Brown
2012-02-27  4:05 Stephen Rothwell
     [not found] <C3AE124F08223B42BC95AEB82F0F6CED1F9D0895@KCHJEXMB01.kpit.com>
2011-12-15  9:25 ` Ashish Jangam
2011-12-15 18:25   ` Grant Likely
2011-12-16  7:19     ` Ashish Jangam
2011-12-16  8:11       ` Grant Likely
2011-12-16  8:15         ` Ashish Jangam
2011-12-16  8:25           ` Grant Likely
2011-12-15  6:17 Stephen Rothwell
2011-12-15  6:05 Stephen Rothwell
2011-12-15  6:17 ` Mark Brown
2011-12-15  6:24   ` Ashish Jangam
2011-09-29  5:18 Stephen Rothwell
2011-09-29  9:43 ` Mark Brown

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=20171102115712.231001ac@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=baolin.wang@linaro$(echo .)org \
    --cc=broonie@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox