From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Extcon build failure in next
Date: Thu, 30 Jun 2016 04:49:12 -0700 [thread overview]
Message-ID: <20160630114911.GO28140@atomide.com> (raw)
In-Reply-To: <3746939.q8kt0ym6m3@wuerfel>
* Arnd Bergmann <arnd@arndb.de> [160630 04:38]:
> On Wednesday, June 29, 2016 10:41:13 PM CEST Tony Lindgren wrote:
> > * Tony Lindgren <tony@atomide.com> [160629 22:41]:
> > > Hi Chanwoo,
> > >
> > > Looks like current Linux next fails to build with at least
> > > omap2plus_defconfig because of:
> > >
> > > ERROR: "extcon_dev_allocate" [drivers/extcon/devres.ko] undefined!
> > > scripts/Makefile.modpost:91: recipe for target '__modpost' failed
> > > make[1]: *** [__modpost] Error 1
> > > Makefile:1163: recipe for target 'modules' failed
> > > make: *** [modules] Error 2
> > > Kernel build failed
> > >
> > > Probably extcon_dev_allocate just needs EXPORT_SYMBOL_GPL?
>
> I've sent "extcon: link devres into core module" for this
OK thanks.
> > Also I'm seeing:
> >
> > drivers/extcon/extcon.c: In function 'extcon_register_notifier':
> > drivers/extcon/extcon.c:455:6: warning: 'idx' may be used uninitialized in this function [-Wmaybe-uninitialized]
> > if (idx >= 0) {
> > ^
>
> I don't see this one. Which compiler version do you use?
Looks like I'm currently using older arm-none-linux-gnueabi-gcc
(Sourcery CodeBench Lite 2014.05-29) 4.8.3 20140320 (prerelease).
I think the Debian compiler was not working few months ago and
I changed to something I had around.
Looks like the warning does not appear with arm-linux-gnueabihf-gcc
(Debian 6.1.1-3) 6.1.1 20160511.
Regards,
Tony
next prev parent reply other threads:[~2016-06-30 11:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 5:37 Extcon build failure in next Tony Lindgren
2016-06-30 5:41 ` Tony Lindgren
2016-06-30 11:37 ` Arnd Bergmann
2016-06-30 11:49 ` Tony Lindgren [this message]
2016-06-30 12:05 ` Arnd Bergmann
2016-06-30 12:23 ` Tony Lindgren
2016-08-03 15:47 ` Geert Uytterhoeven
2016-08-04 0:45 ` Chanwoo Choi
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=20160630114911.GO28140@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).