From: "Kim, Milo" <Milo.Kim@ti.com>
To: Bryan Wu <cooloney@gmail.com>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: linux-next: build failure after merge of the leds tree
Date: Wed, 23 Jan 2013 06:05:17 +0000 [thread overview]
Message-ID: <A874F61F95741C4A9BA573A70FE3998F69E1C225@DQHE02.ent.ti.com> (raw)
In-Reply-To: <20130123151223.01bb155bb06a2e30446900c2@canb.auug.org.au>
> -----Original Message-----
> From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
> Sent: Wednesday, January 23, 2013 1:12 PM
> To: Bryan Wu
> Cc: linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; Kim, Milo
> Subject: linux-next: build failure after merge of the leds tree
>
> Hi Bryan,
>
> After merging the leds tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/built-in.o: In function `lp55xx_unregister_leds':
> (.text+0x161dab): undefined reference to `led_classdev_unregister'
>
> Caused by commit 14732b162d34 ("leds-lp55xx: use
> lp55xx_unregister_leds()").
>
> drivers/built-in.o: In function `lp55xx_init_led':
> leds-lp55xx-common.c:(.text+0x161f23): undefined reference to
> `led_classdev_register'
> leds-lp55xx-common.c:(.text+0x161f9f): undefined reference to
> `led_classdev_unregister'
>
> Caused by commit b5370ff365fa ("eds-lp55xx: use lp55xx_init_led()
> common function").
>
> drivers/built-in.o: In function `lp55xx_read':
> (.text+0x1621b3): undefined reference to `i2c_smbus_read_byte_data'
> drivers/built-in.o: In function `lp55xx_init_device':
> (.text+0x1622f0): undefined reference to `i2c_smbus_write_byte_data'
> drivers/built-in.o: In function `lp55xx_init_device':
> (.text+0x162331): undefined reference to `i2c_smbus_write_byte_data'
> drivers/built-in.o: In function `lp55xx_update_bits':
> (.text+0x162492): undefined reference to `i2c_smbus_write_byte_data'
> drivers/built-in.o: In function `lp55xx_write':
> (.text+0x1624c5): undefined reference to `i2c_smbus_write_byte_data'
>
> Caused by commit 597eb710be87 ("leds-lp55xx: add new common driver for
> lp5521/5523").
>
> I have used the leds tree from next-20130122 for today.
Bryan and Stephen,
Sorry for this errors. A patch has been sent.
https://lkml.org/lkml/2013/1/23/14
And I've got few warnings about leds-lp5521/5523 drivers, separate patchset will
be submitted soon.
Best Regards,
Milo
next prev parent reply other threads:[~2013-01-23 6:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 4:12 linux-next: build failure after merge of the leds tree Stephen Rothwell
2013-01-23 6:05 ` Kim, Milo [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-26 20:53 broonie
2022-09-26 21:18 ` Pavel Machek
2022-09-23 4:31 Stephen Rothwell
2020-01-06 3:21 Stephen Rothwell
2020-01-06 9:31 ` Guido Günther
2020-01-06 10:32 ` Pavel Machek
2020-01-06 15:52 ` Guido Günther
2019-07-25 2:31 Stephen Rothwell
2019-07-25 18:44 ` Jacek Anaszewski
2013-06-17 5:29 Stephen Rothwell
2013-06-17 6:26 ` Alexander Shiyan
2013-06-21 0:16 ` Stephen Rothwell
2013-06-21 0:27 ` Grant Likely
2012-06-13 4:10 Stephen Rothwell
2012-06-13 4:25 ` Bryan Wu
2012-06-08 2:44 Stephen Rothwell
2012-06-08 3:33 ` Bryan Wu
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=A874F61F95741C4A9BA573A70FE3998F69E1C225@DQHE02.ent.ti.com \
--to=milo.kim@ti.com \
--cc=cooloney@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).