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>,
Marek Behun <marek.behun@nic.cz>,
linux-leds@vger.kernel.org
Subject: Re: linux-next: Tree for Apr 29 (drivers/leds/leds-turris-omnia)
Date: Mon, 29 Apr 2019 08:03:02 -0700 [thread overview]
Message-ID: <d3822785-0683-28df-ffa6-ab679aa27c73@infradead.org> (raw)
In-Reply-To: <20190429190354.0d5e2e93@canb.auug.org.au>
On 4/29/19 2:03 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190426:
>
on i386:
when CONFIG_LEDS_TURRIS_OMNIA=y and CONFIG_I2C=m:
Probably should also depend on I2C.
ld: drivers/leds/leds-turris-omnia.o: in function `omnia_leds_remove':
leds-turris-omnia.c:(.text+0xb): undefined reference to `i2c_smbus_write_byte_data'
ld: drivers/leds/leds-turris-omnia.o: in function `omnia_led_brightness_set_blocking':
leds-turris-omnia.c:(.text+0x62): undefined reference to `i2c_smbus_write_byte_data'
ld: drivers/leds/leds-turris-omnia.o: in function `omnia_leds_probe':
leds-turris-omnia.c:(.text+0x1d8): undefined reference to `i2c_smbus_write_byte_data'
ld: leds-turris-omnia.c:(.text+0x1f6): undefined reference to `i2c_smbus_write_byte_data'
ld: drivers/leds/leds-turris-omnia.o: in function `omnia_leds_driver_init':
leds-turris-omnia.c:(.init.text+0x8): undefined reference to `i2c_register_driver'
ld: drivers/leds/leds-turris-omnia.o: in function `omnia_leds_driver_exit':
leds-turris-omnia.c:(.exit.text+0x6): undefined reference to `i2c_del_driver'
--
~Randy
next parent reply other threads:[~2019-04-29 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190429190354.0d5e2e93@canb.auug.org.au>
2019-04-29 15:03 ` Randy Dunlap [this message]
2019-04-29 15:32 ` linux-next: Tree for Apr 29 (drivers/leds/leds-turris-omnia) Pavel Machek
2019-04-29 15:38 ` Marek Behun
2019-04-29 16:37 ` Pavel Machek
2019-04-29 16:44 ` Marek Behun
2019-04-29 16:53 ` Pavel Machek
2019-04-29 17:51 ` Enrico Weigelt, metux IT consult
2019-04-29 18:12 ` Pavel Machek
2019-04-29 18:49 ` Enrico Weigelt, metux IT consult
2019-04-29 19:02 ` Marek Behun
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=d3822785-0683-28df-ffa6-ab679aa27c73@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marek.behun@nic.cz \
--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).