Re: linux-next: build failure after merge of the qcom tree

On Sun 17 May 22:16 PDT 2020, Stephen Rothwell wrote: > Hi all, > > On Mon, 20 Apr 2020 19:41:56 -0700 John Stultz wrote: > > > > On Mon, Apr 20, 2020 at 4:29 PM Stephen Rothwell > > wrote: > > > > > > On Tue, 14 Apr 2020 18:18:11 -0700 John Stultz > > > wrote: > > > > > > > > On Tue, Apr

Re: linux-next: build failure after merge of the qcom tree

Hi all, On Mon, 20 Apr 2020 19:41:56 -0700 John Stultz wrote: > > On Mon, Apr 20, 2020 at 4:29 PM Stephen Rothwell > wrote: > > > > On Tue, 14 Apr 2020 18:18:11 -0700 John Stultz > > wrote: > > > > > > On Tue, Apr 14, 2020 at 5:41 PM Stephen Rothwell > > > wrote: > > > > > > > > After m

Re: linux-next: build failure after merge of the qcom tree

On Wed, Apr 24, 2019 at 09:25:31AM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the qcom tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > arch/arm/boot/dts/qcom-apq8064.dtsi:1297.29-1309.5: ERROR > (phandle_references): /soc/dsi-phy@4700200: Reference

linux-next: build failure after merge of the qcom tree

Hi all, After merging the qcom tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/boot/dts/qcom-apq8064.dtsi:1297.29-1309.5: ERROR (phandle_references): /soc/dsi-phy@4700200: Reference to non-existent node or label "xo_board" Caused by commit 3560af5a56b5 ("AR

Re: linux-next: build failure after merge of the qcom tree

On Thu, Apr 26, 2018 at 04:42:17PM +, Evan Green wrote: > > I suspect that just Linus' tree merged with the qcom tree would have > > been enough to cause the failure. Sorry for missing this in my testing. > > > I've verified that the patch listed above fixes the issue for me. Andy, if > it

Re: linux-next: build failure after merge of the qcom tree

On Wed, Apr 25, 2018 at 9:54 PM Stephen Rothwell wrote: > Hi Evan, > On Thu, 26 Apr 2018 03:39:25 + Evan Green wrote: > > > > Guenter and I had a fix for compile test here, which had failures that > > looked similar: > > > > https://lkml.org/lkml/2018/4/18/752 > That looks like it could ve

Re: linux-next: build failure after merge of the qcom tree

Hi Evan, On Thu, 26 Apr 2018 03:39:25 + Evan Green wrote: > > Guenter and I had a fix for compile test here, which had failures that > looked similar: > > https://lkml.org/lkml/2018/4/18/752 That looks like it could very well be the problem/solution. > I was hoping to verify myself whether

Re: linux-next: build failure after merge of the qcom tree

On Wed, Apr 25, 2018 at 3:42 PM Stephen Rothwell wrote: > Hi Andy, > After merging the qcom tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > ERROR: "geni_se_select_mode" [drivers/tty/serial/qcom_geni_serial.ko] undefined! > ERROR: "geni_se_init" [drivers/tty/serial/qco

linux-next: build failure after merge of the qcom tree

Hi Andy, After merging the qcom tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "geni_se_select_mode" [drivers/tty/serial/qcom_geni_serial.ko] undefined! ERROR: "geni_se_init" [drivers/tty/serial/qcom_geni_serial.ko] undefined! ERROR: "geni_se_config_packing" [driver

linux-next: build failure after merge of the qcom tree

Hi Andy, After merging the qcom tree, today's linux-next build (arm multi_v7_defconfig) failed like this: ERROR (phandle_references): Reference to non-existent node or label "blsp2_dma" ERROR (phandle_references): Reference to non-existent node or label "blsp2_dma" ERROR: Input tree has errors,