From: Eduardo Valentin <eduardo.valentin@ti.com>
To: balbi@ti.com
Cc: Eduardo Valentin <eduardo.valentin@ti.com>,
Tony Lindgren <tony@atomide.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Neil Brown <neilb@suse.de>, Arnd Bergmann <arnd@arndb.de>,
Nicolas Pitre <nico@fluxnic.net>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Durgadoss R <durgadoss.r@intel.com>,
"Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: Latest build results - errors/warnings - lots of them
Date: Thu, 2 May 2013 14:46:31 -0400 [thread overview]
Message-ID: <5182B487.7090801@ti.com> (raw)
In-Reply-To: <20130502180627.GA10672@arwen.pp.htv.fi>
[-- Attachment #1: Type: text/plain, Size: 3960 bytes --]
On 02-05-2013 14:06, Felipe Balbi wrote:
> Hi,
>
> On Thu, May 02, 2013 at 01:07:49PM -0400, Eduardo Valentin wrote:
>> Arnd, Tony,
>>
>> On 02-05-2013 11:38, Tony Lindgren wrote:
>>> * 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).
>>
>> Yeah sure I can fix it. As simple as the following:
>> From c04244c87312f5bfc61d9e12ba3fbaa0fdd81adb Mon Sep 17 00:00:00 2001
>> From: Eduardo Valentin <eduardo.valentin@ti.com>
>> Date: Thu, 2 May 2013 12:58:20 -0400
>> Subject: [PATCH 1/1] thermal: remove stub for thermal_generate_netlink_event
>>
>> This patch removes the stub for thermal_generate_netlink_event
>> because this function is not used anywhere inside the kernel.
>>
>> In case CONFIG_NET is not set we get:
>> include/linux/thermal.h:254:12: warning:
>> 'thermal_generate_netlink_event' defined but not used
>>
>> Thus removing it.
>>
>> Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com>
>> ---
>> include/linux/thermal.h | 6 ------
>> 1 file changed, 6 deletions(-)
>>
>> diff --git a/include/linux/thermal.h b/include/linux/thermal.h
>> index e3c0ae9..e3f3cba 100644
>> --- a/include/linux/thermal.h
>> +++ b/include/linux/thermal.h
>> @@ -250,12 +250,6 @@ void thermal_unregister_governor(struct
>> thermal_governor *);
>> #ifdef CONFIG_NET
>> extern int thermal_generate_netlink_event(struct thermal_zone_device *tz,
>> enum events event);
>> -#else
>> -static int thermal_generate_netlink_event(struct thermal_zone_device *tz,
>
> just adding 'inline' would be an easier patch and lets you compile fine
> on !CONFIG_NET when you starting using thermal_generate_netlink_event().
>
Yeah, that is one thing. But as I pointed, the fix is actually to remove
the whole netlink thing.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 295 bytes --]
next prev parent reply other threads:[~2013-05-02 18:47 UTC|newest]
Thread overview: 26+ 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 11:04 ` Arnd Bergmann
2013-04-30 11:43 ` Dave Martin
2013-04-30 11:54 ` Arnd Bergmann
2013-04-30 15:12 ` Nicolas Pitre
2013-04-30 17:28 ` Dave Martin
2013-04-30 18:18 ` Nicolas Pitre
2013-05-02 8:34 ` Russell King - ARM Linux
2013-05-02 9:46 ` Russell King - ARM Linux
2013-05-02 10:40 ` Dave Martin
2013-04-30 16:11 ` Tony Lindgren
2013-04-30 21:49 ` Tony Lindgren
2013-05-02 6:02 ` Shawn Guo
2013-04-30 23:11 ` Arnd Bergmann
2013-04-30 23:51 ` Tony Lindgren
2013-05-01 0:22 ` Tony Lindgren
2013-05-02 8:22 ` Russell King - ARM Linux
2013-05-02 15:38 ` Tony Lindgren
2013-05-02 17:07 ` Eduardo Valentin
2013-05-02 18:03 ` Arnd Bergmann
2013-05-02 18:45 ` Eduardo Valentin
2013-05-02 18:06 ` Felipe Balbi
2013-05-02 18:46 ` Eduardo Valentin [this message]
2013-05-02 18:54 ` Russell King - ARM Linux
2013-05-06 2:40 ` NeilBrown
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=5182B487.7090801@ti.com \
--to=eduardo.valentin@ti.com \
--cc=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=durgadoss.r@intel.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 \
--cc=rui.zhang@intel.com \
--cc=tony@atomide.com \
/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).