From: Guenter Roeck <linux@roeck-us.net>
To: Josh Boyer <jwboyer@fedoraproject.org>, torvalds@linuxfoundation.org
Cc: Josh Cartwright <joshc@codeaurora.org>,
Pramod Gurav <pramod.gurav@smartplayin.com>,
Bjorn Andersson <bjorn.andersson@sonymobile.com>,
Linus Walleij <linus.walleij@linaro.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: pinctrl-msm build error on Linus' tree
Date: Wed, 8 Oct 2014 16:12:08 -0700 [thread overview]
Message-ID: <20141008231208.GB25134@roeck-us.net> (raw)
In-Reply-To: <CA+5PVA4mO+BiTGvrRb7-MLZRV1iQKsmvaDifFLQiqZN1-b88RQ@mail.gmail.com>
On Wed, Oct 08, 2014 at 06:42:55PM -0400, Josh Boyer wrote:
> We're hitting a build error on ARM with Linus' tree as of Linux
> v3.17-2860-gef0625b70dac :
>
> drivers/pinctrl/qcom/pinctrl-msm.c: In function 'msm_pinctrl_setup_pm_reset':
> drivers/pinctrl/qcom/pinctrl-msm.c:875:4: error: implicit declaration
> of function 'register_restart_handler'
> [-Werror=implicit-function-declaration]
> if (register_restart_handler(&pctrl->restart_nb))
> ^
> drivers/pinctrl/qcom/pinctrl-msm.c: In function 'msm_pinctrl_remove':
> drivers/pinctrl/qcom/pinctrl-msm.c:949:2: error: implicit declaration
> of function 'unregister_restart_handler'
> [-Werror=implicit-function-declaration]
> unregister_restart_handler(&pctrl->restart_nb);
> ^
> cc1: some warnings being treated as errors
>
> Looking at the git logs it seems this was added via:
>
> commit cf1fc187628913070c3e418ce0e205732435aa2f
> Author: Josh Cartwright <joshc@codeaurora.org>
> Date: Tue Sep 23 15:59:53 2014 -0500
>
> pinctrl: qcom: use restart_notifier mechanism for ps_hold
>
>
> However, there is literally nothing else in the tree that calls or
> provides those functions:
>
> [jwboyer@vader linux]$ git grep unregister_restart_handler
> drivers/pinctrl/qcom/pinctrl-msm.c: unregister_restart_handler(&pctrl->resta
> [jwboyer@vader linux]$
>
>
> I'm rather confused. How was this commit built and tested?
>
Looks like the pinctrl tree did not include the merge with the immutable
branch with the necessary infrastructure in its pull request to Linus :-(.
As for how it was tested in the pinctrl tree, no idea. Maybe pinctrl-msm has
some dependency which was missing in the pinctrl tree and came in through
a different pull request.
For this to build, you'll need to merge
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git restart-handler-for-v3.18
which was supposed to be merged by all trees using it, to avoid exactly
this problem (clk, power/restart, and watchdog are the other trees I am
aware of).
Best solution might be for Linus to pull the above tag directly, after
screaming at me appropriately. Sorry, I thought we had this well covered.
Guenter
next prev parent reply other threads:[~2014-10-08 23:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 22:42 Josh Boyer
2014-10-08 22:49 ` Josh Cartwright
2014-10-08 23:09 ` Josh Boyer
2014-10-08 23:18 ` Guenter Roeck
2014-10-08 23:12 ` Guenter Roeck [this message]
2014-10-09 7:34 ` Linus Walleij
2014-10-09 16:07 ` Guenter Roeck
2014-10-10 8:42 ` Linus Walleij
2014-10-10 16:02 ` Guenter Roeck
2014-10-10 16:05 ` Josh Boyer
2014-10-10 16:22 ` Guenter Roeck
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=20141008231208.GB25134@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bjorn.andersson@sonymobile.com \
--cc=joshc@codeaurora.org \
--cc=jwboyer@fedoraproject.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pramod.gurav@smartplayin.com \
--cc=torvalds@linuxfoundation.org \
/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
all inboxes | Powered by JetHome®