From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 21 (regmap-spmi.c caused by QCOM_SPMI_TEMP_ALARM)
Date: Wed, 21 Oct 2015 13:54:22 -0700 [thread overview]
Message-ID: <5627FB7E.60300@infradead.org> (raw)
In-Reply-To: <20151021171623.2d651735@canb.auug.org.au>
On 10/20/15 23:16, Stephen Rothwell wrote:
> Hi all,
>
> There will be no linux-next releases after tomorrow until Nov 2 (kernel
> summit).
>
> Changes since 20151020:
>
on x86_64:
warning: (QCOM_SPMI_TEMP_ALARM) selects REGMAP_SPMI which has unmet direct dependencies (SPMI)
drivers/built-in.o: In function `regmap_spmi_base_read':
regmap-spmi.c:(.text+0x1bef59): undefined reference to `spmi_register_read'
drivers/built-in.o: In function `regmap_spmi_base_gather_write':
regmap-spmi.c:(.text+0x1befd3): undefined reference to `spmi_register_zero_write'
regmap-spmi.c:(.text+0x1bf007): undefined reference to `spmi_register_write'
drivers/built-in.o: In function `regmap_spmi_ext_read':
regmap-spmi.c:(.text+0x1bf106): undefined reference to `spmi_ext_register_read'
regmap-spmi.c:(.text+0x1bf14d): undefined reference to `spmi_ext_register_readl'
drivers/built-in.o: In function `regmap_spmi_ext_gather_write':
regmap-spmi.c:(.text+0x1bf1f6): undefined reference to `spmi_ext_register_write'
regmap-spmi.c:(.text+0x1bf23d): undefined reference to `spmi_ext_register_writel'
CONFIG_REGMAP_SPMI=y
CONFIG_SPMI is not enabled.
CONFIG_QCOM_SPMI_TEMP_ALARM=y
CONFIG_COMPILE_TEST=y
--
~Randy
next prev parent reply other threads:[~2015-10-21 20:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 6:16 linux-next: Tree for Oct 21 Stephen Rothwell
2015-10-21 20:28 ` linux-next: Tree for Oct 21 (drivers/i2c/busses/i2c-designware-platdrv.c) Randy Dunlap
2015-10-22 5:47 ` Jarkko Nikula
2015-10-21 20:54 ` Randy Dunlap [this message]
2015-10-21 22:12 ` linux-next: Tree for Oct 21 (regmap-spmi.c caused by QCOM_SPMI_TEMP_ALARM) Stephen Boyd
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=5627FB7E.60300@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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).