All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Eduardo Valentin <eduardo.valentin@ti.com>,
	Neil Brown <neilb@suse.de>
Cc: Arnd Bergmann <arnd@arndb.de>, Nicolas Pitre <nico@fluxnic.net>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Latest build results - errors/warnings - lots of them
Date: Thu, 2 May 2013 08:38:34 -0700	[thread overview]
Message-ID: <20130502153834.GR28721@atomide.com> (raw)
In-Reply-To: <20130502082218.GA21614@n2100.arm.linux.org.uk>

* Russell King - ARM Linux <linux@arm.linux.org.uk> [130502 01:27]:
> On Tue, Apr 30, 2013 at 09:17:39AM +0100, Russell King - ARM Linux wrote:
> > Latest nightly build of 3.9+my for-next+arm-soc's for-next results in a
> > great load of new warnings and errors.  arch/arm/common/mcpm_head.S,
> > arch/arm/common/mcpm_platsmp.c, arch/arm/common/vlock.S are the biggest
> > source of errors.
> > 
> > OMAP stuff needs a serious look at too - much Kconfig madness there
> > caused by over-use of select, which then goes on to cause build errors
> > because it assumes some stuff is always enabled.
> > 
> > There's also warnings about of_device_id from include/linux/of_platform.h
> > via from arch/arm/kernel/setup.c which feature in all the non-OF builds
> > too which need addressing.
> > 
> > See todays http://www.arm.linux.org.uk/developer/build/ results for all
> > the details and configs.  Not pushing my tree until some of this stuff
> > gets fixed.
> 
> And now we have a new bunch of warnings from OMAP stuff which weren't
> previously there...
> 
> arch/arm/mach-omap2/omap_device.c: In function 'omap_device_get_by_hwmod_name':
> arch/arm/mach-omap2/omap_device.c:821:3: warning: return makes pointer from integer without a cast
> arch/arm/mach-omap2/omap_device.c:826:3: warning: return makes pointer from integer without a cast

Hmm these I already fixed earlier along with a merge resolution, and
I'm not seeing them in next/master or arm-soc/for-next. What do you
have merged into your current tree?

> drivers/power/twl4030_charger.c: In function 'twl4030_charger_enable_usb':
> drivers/power/twl4030_charger.c:192:20: warning: ignoring return value of 'regulator_enable', declared with attribute warn_unused_result

Neil, care to provide a fix for this? It's from your commit ab37813
(twl4030_charger: Allow charger to control the regulator that feeds it).

> include/linux/thermal.h:254:12: warning: 'thermal_generate_netlink_event' defined but not used

Eduardo, can you fix that one? It seems to be from your commit 8ab3e6a
(thermal: Use thermal zone device id in netlink messages).

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Latest build results - errors/warnings - lots of them
Date: Thu, 2 May 2013 08:38:34 -0700	[thread overview]
Message-ID: <20130502153834.GR28721@atomide.com> (raw)
In-Reply-To: <20130502082218.GA21614@n2100.arm.linux.org.uk>

* Russell King - ARM Linux <linux@arm.linux.org.uk> [130502 01:27]:
> On Tue, Apr 30, 2013 at 09:17:39AM +0100, Russell King - ARM Linux wrote:
> > Latest nightly build of 3.9+my for-next+arm-soc's for-next results in a
> > great load of new warnings and errors.  arch/arm/common/mcpm_head.S,
> > arch/arm/common/mcpm_platsmp.c, arch/arm/common/vlock.S are the biggest
> > source of errors.
> > 
> > OMAP stuff needs a serious look at too - much Kconfig madness there
> > caused by over-use of select, which then goes on to cause build errors
> > because it assumes some stuff is always enabled.
> > 
> > There's also warnings about of_device_id from include/linux/of_platform.h
> > via from arch/arm/kernel/setup.c which feature in all the non-OF builds
> > too which need addressing.
> > 
> > See todays http://www.arm.linux.org.uk/developer/build/ results for all
> > the details and configs.  Not pushing my tree until some of this stuff
> > gets fixed.
> 
> And now we have a new bunch of warnings from OMAP stuff which weren't
> previously there...
> 
> arch/arm/mach-omap2/omap_device.c: In function 'omap_device_get_by_hwmod_name':
> arch/arm/mach-omap2/omap_device.c:821:3: warning: return makes pointer from integer without a cast
> arch/arm/mach-omap2/omap_device.c:826:3: warning: return makes pointer from integer without a cast

Hmm these I already fixed earlier along with a merge resolution, and
I'm not seeing them in next/master or arm-soc/for-next. What do you
have merged into your current tree?

> drivers/power/twl4030_charger.c: In function 'twl4030_charger_enable_usb':
> drivers/power/twl4030_charger.c:192:20: warning: ignoring return value of 'regulator_enable', declared with attribute warn_unused_result

Neil, care to provide a fix for this? It's from your commit ab37813
(twl4030_charger: Allow charger to control the regulator that feeds it).

> include/linux/thermal.h:254:12: warning: 'thermal_generate_netlink_event' defined but not used

Eduardo, can you fix that one? It seems to be from your commit 8ab3e6a
(thermal: Use thermal zone device id in netlink messages).

Regards,

Tony

  reply	other threads:[~2013-05-02 15:38 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30  8:17 Latest build results - errors/warnings - lots of them Russell King - ARM Linux
2013-04-30  8:17 ` Russell King - ARM Linux
2013-04-30 11:04 ` Arnd Bergmann
2013-04-30 11:04   ` Arnd Bergmann
2013-04-30 11:43   ` Dave Martin
2013-04-30 11:43     ` Dave Martin
2013-04-30 11:54     ` Arnd Bergmann
2013-04-30 11:54       ` Arnd Bergmann
2013-04-30 15:12     ` Nicolas Pitre
2013-04-30 15:12       ` Nicolas Pitre
2013-04-30 17:28       ` Dave Martin
2013-04-30 17:28         ` Dave Martin
2013-04-30 18:18         ` Nicolas Pitre
2013-04-30 18:18           ` Nicolas Pitre
2013-05-02  8:34           ` Russell King - ARM Linux
2013-05-02  8:34             ` Russell King - ARM Linux
2013-05-02  9:46             ` Russell King - ARM Linux
2013-05-02  9:46               ` Russell King - ARM Linux
2013-05-02 10:40               ` Dave Martin
2013-05-02 10:40                 ` Dave Martin
2013-04-30 16:11   ` Tony Lindgren
2013-04-30 16:11     ` Tony Lindgren
2013-04-30 21:49     ` Tony Lindgren
2013-04-30 21:49       ` Tony Lindgren
2013-05-02  6:02   ` Shawn Guo
2013-05-02  6:02     ` Shawn Guo
2013-04-30 23:11 ` Arnd Bergmann
2013-04-30 23:11   ` Arnd Bergmann
2013-04-30 23:51   ` Tony Lindgren
2013-04-30 23:51     ` Tony Lindgren
2013-05-01  0:22     ` Tony Lindgren
2013-05-01  0:22       ` Tony Lindgren
2013-05-02  8:22 ` Russell King - ARM Linux
2013-05-02  8:22   ` Russell King - ARM Linux
2013-05-02 15:38   ` Tony Lindgren [this message]
2013-05-02 15:38     ` Tony Lindgren
2013-05-02 17:07     ` Eduardo Valentin
2013-05-02 17:07       ` Eduardo Valentin
2013-05-02 18:03       ` Arnd Bergmann
2013-05-02 18:03         ` Arnd Bergmann
2013-05-02 18:45         ` Eduardo Valentin
2013-05-02 18:45           ` Eduardo Valentin
2013-05-02 18:06       ` Felipe Balbi
2013-05-02 18:06         ` Felipe Balbi
2013-05-02 18:46         ` Eduardo Valentin
2013-05-02 18:46           ` Eduardo Valentin
2013-05-02 18:54     ` Russell King - ARM Linux
2013-05-02 18:54       ` Russell King - ARM Linux
2013-05-06  2:40     ` NeilBrown
2013-05-06  2:40       ` NeilBrown
2013-05-08 22:17       ` Tony Lindgren
2013-05-08 22:17         ` Tony Lindgren

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=20130502153834.GR28721@atomide.com \
    --to=tony@atomide.com \
    --cc=arnd@arndb.de \
    --cc=eduardo.valentin@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=neilb@suse.de \
    --cc=nico@fluxnic.net \
    /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.