From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Daniel Lezcano <daniel.lezcano@linaro•org>,
Zhang Rui <rui.zhang@intel•com>,
Eduardo Valentin <edubezval@gmail•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Anson Huang <Anson.Huang@nxp•com>
Subject: linux-next: build warning after merge of the thermal tree
Date: Tue, 3 Mar 2020 10:42:23 +1100 [thread overview]
Message-ID: <20200303104223.73222b9f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
Hi all,
After merging the thermal tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
In file included from drivers/hwmon/hwmon.c:22:
include/linux/thermal.h:382:12: warning: 'thermal_zone_of_get_sensor_id' defined but not used [-Wunused-function]
382 | static int thermal_zone_of_get_sensor_id(struct device_node *tz_np,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
and many more the same ...
Introduced by commit
0629521dc9c9 ("thermal: of-thermal: add API for getting sensor ID from DT")
Missing "inline" in the !defined(CONFIG_THERMAL_OF) update.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-03-02 23:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 23:42 Stephen Rothwell [this message]
2020-03-03 0:17 ` linux-next: build warning after merge of the thermal tree Daniel Lezcano
-- strict thread matches above, loose matches on Subject: below --
2025-05-02 9:07 Stephen Rothwell
2020-10-27 0:34 Stephen Rothwell
2019-10-21 23:23 Stephen Rothwell
2019-10-22 9:50 ` Amit Kucheria
2019-10-22 11:18 ` Stephen Rothwell
2019-10-24 7:26 ` Amit Kucheria
2019-10-29 9:05 ` Geert Uytterhoeven
2019-04-30 3:48 Stephen Rothwell
2017-09-01 0:52 Stephen Rothwell
2016-08-24 3:38 Stephen Rothwell
2016-08-24 7:56 ` Zhang Rui
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=20200303104223.73222b9f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Anson.Huang@nxp$(echo .)com \
--cc=daniel.lezcano@linaro$(echo .)org \
--cc=edubezval@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rui.zhang@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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