From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: linux-next: Tree for Oct 1 (drivers/mfd/simple-mfd-i2c.o)
Date: Thu, 1 Oct 2020 13:12:54 -0700 [thread overview]
Message-ID: <0dca758e-1b61-a4cd-db12-2e2060f7cf60@infradead.org> (raw)
In-Reply-To: <20201001213929.241c1006@canb.auug.org.au>
On 10/1/20 4:39 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200930:
>
on x86_64:
ld: drivers/mfd/simple-mfd-i2c.o: in function `simple_mfd_i2c_probe':
simple-mfd-i2c.c:(.text+0x48): undefined reference to `__devm_regmap_init_i2c'
ld: drivers/mfd/simple-mfd-i2c.o: in function `simple_mfd_i2c_driver_init':
simple-mfd-i2c.c:(.init.text+0x14): undefined reference to `i2c_register_driver'
ld: drivers/mfd/simple-mfd-i2c.o: in function `simple_mfd_i2c_driver_exit':
simple-mfd-i2c.c:(.exit.text+0xd): undefined reference to `i2c_del_driver'
CONFIG_I2C=m
CONFIG_MFD_SIMPLE_MFD_I2C=y
CONFIG_MFD_SL28CPLD=y
Is linux-next missing the source code for CONFIG_MFD_SL28CPLD?
The build error is caused by:
config MFD_SL28CPLD
tristate "Kontron sl28cpld Board Management Controller"
select MFD_SIMPLE_MFD_I2C
that "select" when "depends on I2C" is absent/missing.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2020-10-01 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 11:39 linux-next: Tree for Oct 1 Stephen Rothwell
2020-10-01 20:12 ` Randy Dunlap [this message]
2020-10-02 6:32 ` linux-next: Tree for Oct 1 (drivers/mfd/simple-mfd-i2c.o) Lee Jones
2020-10-02 6:37 ` Randy Dunlap
2020-10-02 6:49 ` Lee Jones
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=0dca758e-1b61-a4cd-db12-2e2060f7cf60@infradead.org \
--to=rdunlap@infradead.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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
all inboxes | Powered by JetHome®