From: "Kim, Milo" <Milo.Kim@ti.com>
To: Randy Dunlap <rdunlap@infradead.org>, Anton Vorontsov <cbou@mail.ru>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"David Woodhouse" <dwmw2@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: RE: [PATCH -next] power: fix lp8788-charger kconfig & build
Date: Wed, 1 May 2013 23:04:38 +0000 [thread overview]
Message-ID: <A874F61F95741C4A9BA573A70FE3998F82E5C1EC@DQHE06.ent.ti.com> (raw)
In-Reply-To: <51816A93.4070802@infradead.org>
> -----Original Message-----
> From: Randy Dunlap [mailto:rdunlap@infradead.org]
> Sent: Thursday, May 02, 2013 4:19 AM
> To: Stephen Rothwell
> Cc: linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; Kim, Milo;
> Anton Vorontsov; David Woodhouse
> Subject: [PATCH -next] power: fix lp8788-charger kconfig & build
>
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix build errors in lp8788-charger by making it depend on IIO.
> Fixes errors when CONFIG_IIO=m and CHARGER_LP8788=y.
>
> lp8788-charger.c:(.text+0x2146b5): undefined reference to
> `iio_channel_get'
> lp8788-charger.c:(.text+0x2146ce): undefined reference to
> `iio_channel_get'
> lp8788-charger.c:(.text+0x214a86): undefined reference to
> `iio_read_channel_processed'
> lp8788-charger.c:(.text+0x214b51): undefined reference to
> `iio_read_channel_processed'
> lp8788-charger.c:(.text+0x214c30): undefined reference to
> `iio_read_channel_processed'
> lp8788-charger.c:(.text+0x214d93): undefined reference to
> `iio_channel_release'
> lp8788-charger.c:(.text+0x214dac): undefined reference to
> `iio_channel_release'
Thanks for fixing this.
Acked-by: Milo Kim <milo.kim@ti.com>
next prev parent reply other threads:[~2013-05-01 23:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 8:37 linux-next: Tree for May 1 Stephen Rothwell
2013-05-01 11:22 ` Sedat Dilek
2013-05-01 17:59 ` linux-next: Tree for May 1 (media/usb/stk1160) Randy Dunlap
2013-05-01 19:28 ` Yann E. MORIN
2013-05-01 19:32 ` Randy Dunlap
2013-05-01 19:58 ` David Rientjes
2013-05-01 20:23 ` Randy Dunlap
2013-05-01 20:40 ` David Rientjes
2013-05-01 20:53 ` Yann E. MORIN
2013-05-01 20:58 ` Randy Dunlap
2013-05-02 14:52 ` Mauro Carvalho Chehab
2013-05-02 21:23 ` Randy Dunlap
2013-05-04 17:21 ` Splitting stk1160-ac97 as a module (Re: linux-next: Tree for May 1 (media/usb/stk1160)) Ezequiel Garcia
2013-05-04 19:59 ` Yann E. MORIN
2013-05-06 13:11 ` Ezequiel Garcia
2013-05-01 18:44 ` [PATCH -next] hid: fix hid-steelseries kconfig/build Randy Dunlap
2013-05-01 19:27 ` simon
2013-05-01 19:39 ` Randy Dunlap
2013-05-01 20:32 ` simon
2013-05-02 6:27 ` [PATCH] HID: hid-steelseries fix led class build issue Simon Wood
2013-05-02 21:50 ` Randy Dunlap
2013-05-02 21:58 ` David Rientjes
2013-05-03 1:43 ` [PATCH-V2] " Simon Wood
2013-05-03 8:27 ` Jiri Kosina
2013-05-02 6:30 ` [PATCH] " Simon Wood
2013-05-01 19:18 ` [PATCH -next] power: fix lp8788-charger kconfig & build Randy Dunlap
2013-05-01 23:04 ` Kim, Milo [this message]
2013-05-03 4:22 ` Anton Vorontsov
2013-05-01 19:27 ` [PATCH -next] staging: sep: fix driver build and kconfig Randy Dunlap
2013-05-02 7:37 ` linux-next: Tree for May 1 ZX
2013-05-02 7:46 ` Hannes Reinecke
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=A874F61F95741C4A9BA573A70FE3998F82E5C1EC@DQHE06.ent.ti.com \
--to=milo.kim@ti.com \
--cc=cbou@mail.ru \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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).