[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALAqxLVN_MZ7XWsg99dhy1=Vde_XSCHey78mrxRuu7a_THxYYw@mail.gmail.com>
Date: Tue, 14 Apr 2020 18:18:11 -0700
From: John Stultz <john.stultz@...aro.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Andy Gross <agross@...nel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Stephen Boyd <swboyd@...omium.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>
Subject: Re: linux-next: build failure after merge of the qcom tree
On Tue, Apr 14, 2020 at 5:41 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> After merging the qcom tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/soc/qcom/rpmh-rsc.c: In function '__tcs_buffer_write':
> drivers/soc/qcom/rpmh-rsc.c:484:3: error: implicit declaration of function 'trace_rpmh_send_msg_rcuidle'; did you mean 'trace_rpmh_send_msg_enabled'? [-Werror=implicit-function-declaration]
> 484 | trace_rpmh_send_msg_rcuidle(drv, tcs_id, j, msgid, cmd);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> | trace_rpmh_send_msg_enabled
> cc1: some warnings being treated as errors
>
> I don't know why this error only started happening today. However
> reverting commit
>
> 1d3c6f86fd3f ("soc: qcom: rpmh: Allow RPMH driver to be loaded as a module")
>
> fixes the build, so I have done that for today.
Ah. I'm guessing the newly added rpmh-rsc code depends on rpmh being built in.
I'll take a look at it.
thanks
-john
Powered by blists - more mailing lists