From: Tony Lindgren <tony@atomide.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Extcon build failure in next
Date: Wed, 29 Jun 2016 22:41:13 -0700 [thread overview]
Message-ID: <20160630054112.GN28140@atomide.com> (raw)
In-Reply-To: <20160630053705.GM28140@atomide.com>
* 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?
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) {
^
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Extcon build failure in next
Date: Wed, 29 Jun 2016 22:41:13 -0700 [thread overview]
Message-ID: <20160630054112.GN28140@atomide.com> (raw)
In-Reply-To: <20160630053705.GM28140@atomide.com>
* 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?
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) {
^
Regards,
Tony
next prev parent reply other threads:[~2016-06-30 5:41 UTC|newest]
Thread overview: 16+ 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:37 ` Tony Lindgren
2016-06-30 5:41 ` Tony Lindgren [this message]
2016-06-30 5:41 ` Tony Lindgren
2016-06-30 11:37 ` Arnd Bergmann
2016-06-30 11:37 ` Arnd Bergmann
2016-06-30 11:49 ` Tony Lindgren
2016-06-30 11:49 ` Tony Lindgren
2016-06-30 12:05 ` Arnd Bergmann
2016-06-30 12:05 ` Arnd Bergmann
2016-06-30 12:23 ` Tony Lindgren
2016-06-30 12:23 ` Tony Lindgren
2016-08-03 15:47 ` Geert Uytterhoeven
2016-08-03 15:47 ` Geert Uytterhoeven
2016-08-04 0:45 ` Chanwoo Choi
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=20160630054112.GN28140@atomide.com \
--to=tony@atomide.com \
--cc=cw00.choi@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.