[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <73acaf57-e74a-ac40-a1f5-9f9aa358b4df@linaro.org>
Date: Wed, 21 Jun 2017 11:54:26 +0300
From: Stanimir Varbanov <stanimir.varbanov@...aro.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Mauro Carvalho Chehab <mchehab@....samsung.com>
Cc: Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Hans Verkuil <hans.verkuil@...co.com>
Subject: Re: linux-next: build failure after merge of the v4l-dvb tree
Hi Stephen,
On 06/21/2017 04:25 AM, Stephen Rothwell wrote:
> Hi Mauro,
>
> After merging the v4l-dvb tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "qcom_scm_is_available" [drivers/media/platform/qcom/venus/venus-core.ko] undefined!
> ERROR: "qcom_scm_pas_shutdown" [drivers/media/platform/qcom/venus/venus-core.ko] undefined!
> ERROR: "qcom_scm_set_remote_state" [drivers/media/platform/qcom/venus/venus-core.ko] undefined!
>
> Caused by commits
>
> af2c3834c8ca ("[media] media: venus: adding core part and helper functions")
> d96d3f30c0f2 ("[media] media: venus: hfi: add Venus HFI files")
> 703528005e58 ("[media] media: venus: enable building of Venus video driver")
>
> I have merged the 4vl-dvb tree from next-20170620 for today.
>
I've investigated this and the issue comes from this commit:
d4348b43bbcadb6d5faee36024245944b6600d25 firmware: qcom_scm: Fix to
allow COMPILE_TEST-ing
which is from Andy's qcom git tree, I asked Andy to drop this patch
because it was rejected.
I also manually merged v4l-dvb:master and reverted above commit. After
that allmodconfig builds fine and the subject error from venus driver
disappeared.
Sorry for inconvenience.
--
regards,
Stan
Powered by blists - more mailing lists