From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jenny TC <jenny.tc@intel.com>, Jean Delvare <khali@linux-fr.org>,
Andrew Morton <akpm@linux-foundation.org>,
Len Brown <len.brown@intel.com>
Subject: Re: linux-next: build warning after merge of the battery tree
Date: Mon, 18 Jun 2012 22:02:36 -0700 [thread overview]
Message-ID: <20120619050236.GA16286@lizard> (raw)
In-Reply-To: <20120619145408.4c68bff2ed75b52fdba66eff@canb.auug.org.au>
Hi Stephen,
On Tue, Jun 19, 2012 at 02:54:08PM +1000, Stephen Rothwell wrote:
> After merging the battery tree, today's linux-next build (i386 defconfig)
> produced this warning:
>
> drivers/power/power_supply_core.c: In function 'psy_register_thermal':
> drivers/power/power_supply_core.c:204:6: warning: passing argument 1 of 'thermal_zone_device_register' discards 'const' qualifier from pointer target type [enabled by default]
> include/linux/thermal.h:149:29: note: expected 'char *' but argument is of type 'const char *'
>
> Introduced by commit 3be330bf8860 ("power_supply: Register battery as a
> thermal zone").
Yup, at the same time as I merged the thermal zone support for
power supply class, I also fixed the root cause of the warning:
http://lkml.org/lkml/2012/6/18/28
But I guess it will go via -mm tree. Or should/can I take it into
battery-2.6 tree? Added Cc's.
Thanks!
--
Anton Vorontsov
Email: cbouatmailru@gmail.com
next prev parent reply other threads:[~2012-06-19 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 4:54 linux-next: build warning after merge of the battery tree Stephen Rothwell
2012-06-19 5:02 ` Anton Vorontsov [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-25 4:22 Stephen Rothwell
2014-09-25 7:00 ` Krzysztof Kozlowski
2017-01-05 1:53 Stephen Rothwell
2017-01-05 23:29 ` Sebastian Reichel
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=20120619050236.GA16286@lizard \
--to=cbouatmailru@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jenny.tc@intel.com \
--cc=khali@linux-fr.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 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.