From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Eduardo Valentin <edubezval@gmail•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Caesar Wang <wxt@rock-chips•com>
Subject: linux-next: build failure after merge of the thermal-soc tree
Date: Thu, 5 Nov 2015 16:01:13 +1100 [thread overview]
Message-ID: <20151105160113.5d6f73f7@canb.auug.org.au> (raw)
Hi Eduardo,
After merging the thermal-soc tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/thermal/rockchip_thermal.c: In function 'rockchip_thermal_suspend':
drivers/thermal/rockchip_thermal.c:641:2: error: implicit declaration of function 'pinctrl_pm_select_sleep_state' [-Werror=implicit-function-declaration]
pinctrl_pm_select_sleep_state(dev);
^
drivers/thermal/rockchip_thermal.c: In function 'rockchip_thermal_resume':
drivers/thermal/rockchip_thermal.c:679:2: error: implicit declaration of function 'pinctrl_pm_select_default_state' [-Werror=implicit-function-declaration]
pinctrl_pm_select_default_state(dev);
^
Caused by commit
7e38a5b1daa1 ("thermal: rockchip: support the sleep pinctrl state to avoid glitches")
Probably just a missing include file.
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
next reply other threads:[~2015-11-05 5:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 5:01 Stephen Rothwell [this message]
2015-11-05 10:22 ` linux-next: build failure after merge of the thermal-soc tree Caesar Wang
2015-11-09 19:17 ` Eduardo Valentin
-- strict thread matches above, loose matches on Subject: below --
2019-05-13 1:02 Stephen Rothwell
2019-05-13 15:57 ` Guenter Roeck
2015-12-31 1:53 Stephen Rothwell
2015-12-31 17:01 ` Srinivas Pandruvada
2015-03-04 7:06 Stephen Rothwell
2015-03-04 19:01 ` Eduardo Valentin
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=20151105160113.5d6f73f7@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=edubezval@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=wxt@rock-chips$(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