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

[Hector Martin]

Hi Stephen,

On 09/04/2021 19.13, Stephen Rothwell wrote:

Hi all,

After merging the arm-soc tree, today's linux-next build (powerpc
allnoconfig) failed like this:


[...]

Caused by commits

   7c566bb5e4d5 ("asm-generic/io.h:  Add a non-posted variant of ioremap()")
   89897f739d7b ("of/address: Add infrastructure to declare MMIO as non-posted")
(and maybe some others)

I have reverted 86332e9e3477..7d2d16ccf15d for today.


This is fixed in ea9629283839 in the soc tree, which went in a few hours 
ago. Sorry for the noise.


--
Hector Martin (mar...@marcan.st)
Public Key: https://mrcn.st/pub

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

[Maxime Ripard]

On Tue, Nov 24, 2020 at 10:18:04AM +0100, Christoph Hellwig wrote:
> On Tue, Nov 24, 2020 at 09:31:15AM +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the arm-soc tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> > 
> > drivers/soc/sunxi/sunxi_mbus.c: In function 'sunxi_mbus_notifier':
> > drivers/soc/sunxi/sunxi_mbus.c:93:8: error: implicit declaration of 
> > function 'dma_direct_set_offset' [-Werror=implicit-function-declaration]
> >93 |  ret = dma_direct_set_offset(dev, PHYS_OFFSET, 0, SZ_4G);
> >   |^
> > 
> > Caused by commit
> > 
> >   b4bdc4fbf8d0 ("soc: sunxi: Deal with the MBUS DMA offsets in a central 
> > place")
> > 
> > probably interacting with commit
> > 
> >   16fee29b0735 ("dma-mapping: remove the dma_direct_set_offset export")
> > 
> > which is also in the arm-soc tree ...
> 
> drivers/soc/sunxi/sunxi_mbus.c now needs an include of .

I just sent a patch doing so

Maxime


signature.asc
Description: PGP signature

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

[Christoph Hellwig]

On Tue, Nov 24, 2020 at 09:31:15AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the arm-soc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> drivers/soc/sunxi/sunxi_mbus.c: In function 'sunxi_mbus_notifier':
> drivers/soc/sunxi/sunxi_mbus.c:93:8: error: implicit declaration of function 
> 'dma_direct_set_offset' [-Werror=implicit-function-declaration]
>93 |  ret = dma_direct_set_offset(dev, PHYS_OFFSET, 0, SZ_4G);
>   |^
> 
> Caused by commit
> 
>   b4bdc4fbf8d0 ("soc: sunxi: Deal with the MBUS DMA offsets in a central 
> place")
> 
> probably interacting with commit
> 
>   16fee29b0735 ("dma-mapping: remove the dma_direct_set_offset export")
> 
> which is also in the arm-soc tree ...

drivers/soc/sunxi/sunxi_mbus.c now needs an include of .

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

[Arnd Bergmann]

On Wed, Aug 14, 2019 at 12:50 AM Stephen Rothwell  wrote:
>
> Hi all,
>
> After merging the arm-soc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> arch/arm/Kconfig:720: syntax error
> arch/arm/Kconfig:719: invalid statement
> arch/arm/Kconfig:720: can't open file "arch/arm/mach-ks8695/Kconfig"
>
> Caused by commit
>
>   eb4f78f8b8cb ("ARM: remove ks8695 platform")
>
> I applied the following patch for today
>
> From: Stephen Rothwell 
> Date: Wed, 14 Aug 2019 08:46:39 +1000
> Subject: [PATCH] arm-soc: fix up bad rebase?
>
> Signed-off-by: Stephen Rothwell 


Thanks for the report. I folded your fix into the original patch now.

   Arnd

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

[Robert Jarzmik]

Olof Johansson  writes:

> It's a known issue due to dependencies with a driver tree. :(
>
> Robert, this is unfortunate. What's the dependent patches? We can pick
> them up in our tree as duplicates if needed.
I'd rather postpone one of the patches, as I explained in the pull request.
As Stephen noticed, this will be :
0d0b16b8e008 ("dmaengine: pxa: make the filter function internal")

I'll queue this one for the 4.20 cycle. By the way, all of this cames from the
fact that I didn't take this very patch in my imutable branch for this change
...

I'll also resend a pull request, without this patch if that's good for you,
which will solve the breakage.

Cheers.

-- 
Robert

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

[Robert Jarzmik]

Olof Johansson  writes:

> It's a known issue due to dependencies with a driver tree. :(
>
> Robert, this is unfortunate. What's the dependent patches? We can pick
> them up in our tree as duplicates if needed.
I'd rather postpone one of the patches, as I explained in the pull request.
As Stephen noticed, this will be :
0d0b16b8e008 ("dmaengine: pxa: make the filter function internal")

I'll queue this one for the 4.20 cycle. By the way, all of this cames from the
fact that I didn't take this very patch in my imutable branch for this change
...

I'll also resend a pull request, without this patch if that's good for you,
which will solve the breakage.

Cheers.

-- 
Robert

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

[Olof Johansson]

On Sun, Jul 15, 2018 at 4:50 PM, Olof Johansson  wrote:
> On Sun, Jul 15, 2018 at 4:13 PM, Stephen Rothwell  
> wrote:
>> Hi all,
>>
>> After merging the arm-soc tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> sound/arm/pxa2xx-pcm-lib.c: In function '__pxa2xx_pcm_open':
>> sound/arm/pxa2xx-pcm-lib.c:129:6: error: 'pxad_filter_fn' undeclared (first 
>> use in this function); did you mean 'dma_filter_fn'?
>>   pxad_filter_fn,
>>   ^~
>>   dma_filter_fn
>>
>> Caused by commit
>>
>>   0d0b16b8e008 ("dmaengine: pxa: make the filter function internal")
>>
>> I have used the arm-soc tree from next-20180713 for today.
>
> It's a known issue due to dependencies with a driver tree. :(
>
> Robert, this is unfortunate. What's the dependent patches? We can pick
> them up in our tree as duplicates if needed.

Ok, it was easy to drop PXA this time around, so I've done that.
Stephen; arm-soc/for-next should be building again (for tomorrow).


Thanks,

-Olof

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

[Olof Johansson]

On Sun, Jul 15, 2018 at 4:50 PM, Olof Johansson  wrote:
> On Sun, Jul 15, 2018 at 4:13 PM, Stephen Rothwell  
> wrote:
>> Hi all,
>>
>> After merging the arm-soc tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> sound/arm/pxa2xx-pcm-lib.c: In function '__pxa2xx_pcm_open':
>> sound/arm/pxa2xx-pcm-lib.c:129:6: error: 'pxad_filter_fn' undeclared (first 
>> use in this function); did you mean 'dma_filter_fn'?
>>   pxad_filter_fn,
>>   ^~
>>   dma_filter_fn
>>
>> Caused by commit
>>
>>   0d0b16b8e008 ("dmaengine: pxa: make the filter function internal")
>>
>> I have used the arm-soc tree from next-20180713 for today.
>
> It's a known issue due to dependencies with a driver tree. :(
>
> Robert, this is unfortunate. What's the dependent patches? We can pick
> them up in our tree as duplicates if needed.

Ok, it was easy to drop PXA this time around, so I've done that.
Stephen; arm-soc/for-next should be building again (for tomorrow).


Thanks,

-Olof

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

[Olof Johansson]

On Sun, Jul 15, 2018 at 4:13 PM, Stephen Rothwell  wrote:
> Hi all,
>
> After merging the arm-soc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> sound/arm/pxa2xx-pcm-lib.c: In function '__pxa2xx_pcm_open':
> sound/arm/pxa2xx-pcm-lib.c:129:6: error: 'pxad_filter_fn' undeclared (first 
> use in this function); did you mean 'dma_filter_fn'?
>   pxad_filter_fn,
>   ^~
>   dma_filter_fn
>
> Caused by commit
>
>   0d0b16b8e008 ("dmaengine: pxa: make the filter function internal")
>
> I have used the arm-soc tree from next-20180713 for today.

It's a known issue due to dependencies with a driver tree. :(

Robert, this is unfortunate. What's the dependent patches? We can pick
them up in our tree as duplicates if needed.


-Olof

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

[Olof Johansson]

On Sun, Jul 15, 2018 at 4:13 PM, Stephen Rothwell  wrote:
> Hi all,
>
> After merging the arm-soc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> sound/arm/pxa2xx-pcm-lib.c: In function '__pxa2xx_pcm_open':
> sound/arm/pxa2xx-pcm-lib.c:129:6: error: 'pxad_filter_fn' undeclared (first 
> use in this function); did you mean 'dma_filter_fn'?
>   pxad_filter_fn,
>   ^~
>   dma_filter_fn
>
> Caused by commit
>
>   0d0b16b8e008 ("dmaengine: pxa: make the filter function internal")
>
> I have used the arm-soc tree from next-20180713 for today.

It's a known issue due to dependencies with a driver tree. :(

Robert, this is unfortunate. What's the dependent patches? We can pick
them up in our tree as duplicates if needed.


-Olof

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

[Arnd Bergmann]

On Tuesday 26 April 2016 10:51:50 Stephen Rothwell wrote:
> Hi Arnd,
> 
> On Tue, 26 Apr 2016 01:54:20 +0200 Arnd Bergmann  wrote:
> >
> > Ah, sorry about that. I think I fixed it up just as you pulled it in.
> > If you don't mind, could you try pulling the tree once more on top
> > of what you have?
> 
> Sorry, but I need to keep going if I am to finish each day.  I will
> fetch it for tomorrow, though.  If I finish early enough, I will see if
> I can fetch and merge it at the end ...
> 

Ok, fair enough. I've now merged the latest arm-soc/for-next branch with
today's linux-next to give it some extra time on the test infrastructure.

Arnd

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

[Arnd Bergmann]

On Tuesday 26 April 2016 10:51:50 Stephen Rothwell wrote:
> Hi Arnd,
> 
> On Tue, 26 Apr 2016 01:54:20 +0200 Arnd Bergmann  wrote:
> >
> > Ah, sorry about that. I think I fixed it up just as you pulled it in.
> > If you don't mind, could you try pulling the tree once more on top
> > of what you have?
> 
> Sorry, but I need to keep going if I am to finish each day.  I will
> fetch it for tomorrow, though.  If I finish early enough, I will see if
> I can fetch and merge it at the end ...
> 

Ok, fair enough. I've now merged the latest arm-soc/for-next branch with
today's linux-next to give it some extra time on the test infrastructure.

Arnd

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

[Stephen Rothwell]

Hi Arnd,

On Tue, 26 Apr 2016 01:54:20 +0200 Arnd Bergmann  wrote:
>
> Ah, sorry about that. I think I fixed it up just as you pulled it in.
> If you don't mind, could you try pulling the tree once more on top
> of what you have?

Sorry, but I need to keep going if I am to finish each day.  I will
fetch it for tomorrow, though.  If I finish early enough, I will see if
I can fetch and merge it at the end ...

-- 
Cheers,
Stephen Rothwell

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

[Stephen Rothwell]

Hi Arnd,

On Tue, 26 Apr 2016 01:54:20 +0200 Arnd Bergmann  wrote:
>
> Ah, sorry about that. I think I fixed it up just as you pulled it in.
> If you don't mind, could you try pulling the tree once more on top
> of what you have?

Sorry, but I need to keep going if I am to finish each day.  I will
fetch it for tomorrow, though.  If I finish early enough, I will see if
I can fetch and merge it at the end ...

-- 
Cheers,
Stephen Rothwell

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

[Arnd Bergmann]

On Tuesday 26 April 2016 09:43:31 Stephen Rothwell wrote:
> Hi all,
> 
> After merging the arm-soc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> ERROR: "of_flash_probe_versatile" [drivers/mtd/maps/physmap_of.ko] undefined!
> 
> Caused by commit
> 
>   b0afd44bc192 ("mtd: physmap_of: add a hook for Versatile write protection")
> 
> I used the arm-soc tree from next-20160422 for today.
> 

Ah, sorry about that. I think I fixed it up just as you pulled it in.
If you don't mind, could you try pulling the tree once more on top
of what you have?

Arnd

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

[Arnd Bergmann]

On Tuesday 26 April 2016 09:43:31 Stephen Rothwell wrote:
> Hi all,
> 
> After merging the arm-soc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> ERROR: "of_flash_probe_versatile" [drivers/mtd/maps/physmap_of.ko] undefined!
> 
> Caused by commit
> 
>   b0afd44bc192 ("mtd: physmap_of: add a hook for Versatile write protection")
> 
> I used the arm-soc tree from next-20160422 for today.
> 

Ah, sorry about that. I think I fixed it up just as you pulled it in.
If you don't mind, could you try pulling the tree once more on top
of what you have?

Arnd

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

[Arnd Bergmann]

On Thursday 15 October 2015 10:40:45 Jisheng Zhang wrote:
> On Thu, 15 Oct 2015 10:19:20 +1100
> Stephen Rothwell  wrote:
> 
> > Hi all,
> > 
> > After merging the arm-soc tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> > 
> > arch/arm/boot/dts/berlin2q.dtsi:62.24-25 syntax error
> > FATAL ERROR: Unable to parse input tree
> 
> I just checked, this is caused by missing the following two commits
> 
> f72d787d9287 ("clk: berlin: move MAX_CLKS out of drivers/clk/berlin")
> 
> 44b2e5f96d5e ("clk: berlin: add cpuclk")

I've reverted 23998645f6e73 ("ARM: berlin: dts: add the cpufreq-dt
bindings on the BG2Q") on my for-next branch for the time being, to
get a working tree again and am waiting for a proper fixup patch
from Sebastian now to rectify the next/dt branch.

Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Arnd Bergmann]

On Thursday 15 October 2015 10:19:20 Stephen Rothwell wrote:
> 
> After merging the arm-soc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> arch/arm/boot/dts/berlin2q.dtsi:62.24-25 syntax error
> FATAL ERROR: Unable to parse input tree
> 
> I can't see what caused this error, so I have just used the arm-soc tree
> from next-20151013 for today.
> 
> 

Thanks a lot, I've merged a broken branch that was based on the
wrong start point.

Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Arnd Bergmann]

On Thursday 15 October 2015 10:40:45 Jisheng Zhang wrote:
> On Thu, 15 Oct 2015 10:19:20 +1100
> Stephen Rothwell  wrote:
> 
> > Hi all,
> > 
> > After merging the arm-soc tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> > 
> > arch/arm/boot/dts/berlin2q.dtsi:62.24-25 syntax error
> > FATAL ERROR: Unable to parse input tree
> 
> I just checked, this is caused by missing the following two commits
> 
> f72d787d9287 ("clk: berlin: move MAX_CLKS out of drivers/clk/berlin")
> 
> 44b2e5f96d5e ("clk: berlin: add cpuclk")

I've reverted 23998645f6e73 ("ARM: berlin: dts: add the cpufreq-dt
bindings on the BG2Q") on my for-next branch for the time being, to
get a working tree again and am waiting for a proper fixup patch
from Sebastian now to rectify the next/dt branch.

Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Arnd Bergmann]

On Thursday 15 October 2015 10:19:20 Stephen Rothwell wrote:
> 
> After merging the arm-soc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> arch/arm/boot/dts/berlin2q.dtsi:62.24-25 syntax error
> FATAL ERROR: Unable to parse input tree
> 
> I can't see what caused this error, so I have just used the arm-soc tree
> from next-20151013 for today.
> 
> 

Thanks a lot, I've merged a broken branch that was based on the
wrong start point.

Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Jisheng Zhang]

Dear all,

On Thu, 15 Oct 2015 10:19:20 +1100
Stephen Rothwell  wrote:

> Hi all,
> 
> After merging the arm-soc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> arch/arm/boot/dts/berlin2q.dtsi:62.24-25 syntax error
> FATAL ERROR: Unable to parse input tree

I just checked, this is caused by missing the following two commits

f72d787d9287 ("clk: berlin: move MAX_CLKS out of drivers/clk/berlin")

44b2e5f96d5e ("clk: berlin: add cpuclk")

Thanks,
Jisheng

> 
> I can't see what caused this error, so I have just used the arm-soc tree
> from next-20151013 for today.
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Jisheng Zhang]

Dear all,

On Thu, 15 Oct 2015 10:19:20 +1100
Stephen Rothwell  wrote:

> Hi all,
> 
> After merging the arm-soc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> arch/arm/boot/dts/berlin2q.dtsi:62.24-25 syntax error
> FATAL ERROR: Unable to parse input tree

I just checked, this is caused by missing the following two commits

f72d787d9287 ("clk: berlin: move MAX_CLKS out of drivers/clk/berlin")

44b2e5f96d5e ("clk: berlin: add cpuclk")

Thanks,
Jisheng

> 
> I can't see what caused this error, so I have just used the arm-soc tree
> from next-20151013 for today.
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Kevin Hilman]

Michael Ellerman  writes:

> Hi all,
>
> After merging the arm-soc tree, today's linux-next build 
> (arm_multi_v7_defconfig)
> failed like this:
>
>   scripts/Makefile.build:258: recipe for target 
> 'arch/arm/mach-socfpga/platsmp.o' failed
>   arch/arm/mach-socfpga/platsmp.c:66:23: error: 'socfpga_secondary_startup' 
> undeclared (first use in this function)
>  writel(virt_to_phys(socfpga_secondary_startup),
>^
>
> Caused by the interaction of commits 45be0cdb5323 "ARM: socfpga: add
> CPU_METHOD_OF_DECLARE for Arria 10" and 02b4e2756e01 "ARM: v7 setup function
> should invalidate L1 cache".

I found this as well, unfortunately after it was already pulled for -next.

> I applied the following fix for today.

Yes, that's the right fix, and arm-soc now has the equivalent fix as
well.

Thanks,

Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Kevin Hilman]

Michael Ellerman m...@ellerman.id.au writes:

 Hi all,

 After merging the arm-soc tree, today's linux-next build 
 (arm_multi_v7_defconfig)
 failed like this:

   scripts/Makefile.build:258: recipe for target 
 'arch/arm/mach-socfpga/platsmp.o' failed
   arch/arm/mach-socfpga/platsmp.c:66:23: error: 'socfpga_secondary_startup' 
 undeclared (first use in this function)
  writel(virt_to_phys(socfpga_secondary_startup),
^

 Caused by the interaction of commits 45be0cdb5323 ARM: socfpga: add
 CPU_METHOD_OF_DECLARE for Arria 10 and 02b4e2756e01 ARM: v7 setup function
 should invalidate L1 cache.

I found this as well, unfortunately after it was already pulled for -next.

 I applied the following fix for today.

Yes, that's the right fix, and arm-soc now has the equivalent fix as
well.

Thanks,

Kevin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Arnd Bergmann]

On Tuesday 14 April 2015 09:47:35 Stephen Rothwell wrote:
> Hi all,
> 
> On Wed, 8 Apr 2015 16:59:49 +0200 Matthias Brugger  
> wrote:
> >
> > 2015-04-08 16:49 GMT+02:00 Linus Walleij :
> > > On Tue, Apr 7, 2015 at 2:28 PM, Arnd Bergmann  wrote:
> > >> On Tuesday 07 April 2015 11:28:22 Linus Walleij wrote:
> > >>> On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
> > >>>  wrote:
> > >>> > 2015-04-07 3:12 GMT+02:00 Stephen Rothwell :
> > >>> >> Hi all,
> > >>> >>
> > >>> >> After merging the arm-soc tree, today's linux-next build (arm
> > >>> >> multi_v7_defconfig) failed like this:
> > >>> >>
> > >>> >> In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
> > >>> >>  from arch/arm/boot/dts/mt8135-evbp1.dts:16:
> > >>> >> arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
> > >>> >> dt-bindings/pinctrl/mt65xx.h: No such file or directory
> > >>> >>  #include 
> > >>> >> ^
> > >>> >>
> > >>> >> Caused by commit e6f219b8ec5e ("ARM: dts: mt8135: Add 
> > >>> >> pinctrl/GPIO/EINT
> > >>> >> node for mt8135").
> > >>> >
> > >>> > This will be fixed as soon as Linus pinctrl for-next branch got 
> > >>> > merged [1].
> > >>>
> > >>> Hm that's unfortunate, we do not rely on merge orders.
> > >>>
> > >>> Either the ARM SoC tree needs to pull in the pinctrl commit
> > >>> or I need to carry this patch in the pinctrl tree.
> > >>>
> > >>> Is this sufficiently stand-alone to be merged into my tree
> > >>> or do you need to go by the former approach?
> > >>
> > >> Let's just delay this patch to another merge window. You can add the
> > >> driver now, and we should just revert the DT node addition in arm-soc,
> > >> and then we'll add it in 4.2, or come up with a better solution.
> > >
> > > OK. I'm not applying it then.
> > 
> > @arnd: I will send the patch in the next merge window then. Do you
> > want me to do anything else for this merge window (e.g. resend the
> > pull request without the patch)?
> 
> I am still applying my reversion patch to the arm-soc tree merge ...

Sorry about that. I've applied the same revert now to our branch, but
there are some other fixes that I need to apply too before I upload
it. If you don't mind pulling arm-soc again manually at the end
of your merges for today, that might be helpful, otherwise it should
be fixed tomorrow.

Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Stephen Rothwell]

Hi all,

On Wed, 8 Apr 2015 16:59:49 +0200 Matthias Brugger  
wrote:
>
> 2015-04-08 16:49 GMT+02:00 Linus Walleij :
> > On Tue, Apr 7, 2015 at 2:28 PM, Arnd Bergmann  wrote:
> >> On Tuesday 07 April 2015 11:28:22 Linus Walleij wrote:
> >>> On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
> >>>  wrote:
> >>> > 2015-04-07 3:12 GMT+02:00 Stephen Rothwell :
> >>> >> Hi all,
> >>> >>
> >>> >> After merging the arm-soc tree, today's linux-next build (arm
> >>> >> multi_v7_defconfig) failed like this:
> >>> >>
> >>> >> In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
> >>> >>  from arch/arm/boot/dts/mt8135-evbp1.dts:16:
> >>> >> arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
> >>> >> dt-bindings/pinctrl/mt65xx.h: No such file or directory
> >>> >>  #include 
> >>> >> ^
> >>> >>
> >>> >> Caused by commit e6f219b8ec5e ("ARM: dts: mt8135: Add pinctrl/GPIO/EINT
> >>> >> node for mt8135").
> >>> >
> >>> > This will be fixed as soon as Linus pinctrl for-next branch got merged 
> >>> > [1].
> >>>
> >>> Hm that's unfortunate, we do not rely on merge orders.
> >>>
> >>> Either the ARM SoC tree needs to pull in the pinctrl commit
> >>> or I need to carry this patch in the pinctrl tree.
> >>>
> >>> Is this sufficiently stand-alone to be merged into my tree
> >>> or do you need to go by the former approach?
> >>
> >> Let's just delay this patch to another merge window. You can add the
> >> driver now, and we should just revert the DT node addition in arm-soc,
> >> and then we'll add it in 4.2, or come up with a better solution.
> >
> > OK. I'm not applying it then.
> 
> @arnd: I will send the patch in the next merge window then. Do you
> want me to do anything else for this merge window (e.g. resend the
> pull request without the patch)?

I am still applying my reversion patch to the arm-soc tree merge ...

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au


pgp2iSARRW5w8.pgp
Description: OpenPGP digital signature

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

[Arnd Bergmann]

On Tuesday 14 April 2015 09:47:35 Stephen Rothwell wrote:
 Hi all,
 
 On Wed, 8 Apr 2015 16:59:49 +0200 Matthias Brugger matthias@gmail.com 
 wrote:
 
  2015-04-08 16:49 GMT+02:00 Linus Walleij linus.wall...@linaro.org:
   On Tue, Apr 7, 2015 at 2:28 PM, Arnd Bergmann a...@arndb.de wrote:
   On Tuesday 07 April 2015 11:28:22 Linus Walleij wrote:
   On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
   matthias@gmail.com wrote:
2015-04-07 3:12 GMT+02:00 Stephen Rothwell s...@canb.auug.org.au:
Hi all,
   
After merging the arm-soc tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
   
In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
 from arch/arm/boot/dts/mt8135-evbp1.dts:16:
arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
dt-bindings/pinctrl/mt65xx.h: No such file or directory
 #include dt-bindings/pinctrl/mt65xx.h
^
   
Caused by commit e6f219b8ec5e (ARM: dts: mt8135: Add 
pinctrl/GPIO/EINT
node for mt8135).
   
This will be fixed as soon as Linus pinctrl for-next branch got 
merged [1].
  
   Hm that's unfortunate, we do not rely on merge orders.
  
   Either the ARM SoC tree needs to pull in the pinctrl commit
   or I need to carry this patch in the pinctrl tree.
  
   Is this sufficiently stand-alone to be merged into my tree
   or do you need to go by the former approach?
  
   Let's just delay this patch to another merge window. You can add the
   driver now, and we should just revert the DT node addition in arm-soc,
   and then we'll add it in 4.2, or come up with a better solution.
  
   OK. I'm not applying it then.
  
  @arnd: I will send the patch in the next merge window then. Do you
  want me to do anything else for this merge window (e.g. resend the
  pull request without the patch)?
 
 I am still applying my reversion patch to the arm-soc tree merge ...

Sorry about that. I've applied the same revert now to our branch, but
there are some other fixes that I need to apply too before I upload
it. If you don't mind pulling arm-soc again manually at the end
of your merges for today, that might be helpful, otherwise it should
be fixed tomorrow.

Arnd
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Stephen Rothwell]

Hi all,

On Wed, 8 Apr 2015 16:59:49 +0200 Matthias Brugger matthias@gmail.com 
wrote:

 2015-04-08 16:49 GMT+02:00 Linus Walleij linus.wall...@linaro.org:
  On Tue, Apr 7, 2015 at 2:28 PM, Arnd Bergmann a...@arndb.de wrote:
  On Tuesday 07 April 2015 11:28:22 Linus Walleij wrote:
  On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
  matthias@gmail.com wrote:
   2015-04-07 3:12 GMT+02:00 Stephen Rothwell s...@canb.auug.org.au:
   Hi all,
  
   After merging the arm-soc tree, today's linux-next build (arm
   multi_v7_defconfig) failed like this:
  
   In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
from arch/arm/boot/dts/mt8135-evbp1.dts:16:
   arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
   dt-bindings/pinctrl/mt65xx.h: No such file or directory
#include dt-bindings/pinctrl/mt65xx.h
   ^
  
   Caused by commit e6f219b8ec5e (ARM: dts: mt8135: Add pinctrl/GPIO/EINT
   node for mt8135).
  
   This will be fixed as soon as Linus pinctrl for-next branch got merged 
   [1].
 
  Hm that's unfortunate, we do not rely on merge orders.
 
  Either the ARM SoC tree needs to pull in the pinctrl commit
  or I need to carry this patch in the pinctrl tree.
 
  Is this sufficiently stand-alone to be merged into my tree
  or do you need to go by the former approach?
 
  Let's just delay this patch to another merge window. You can add the
  driver now, and we should just revert the DT node addition in arm-soc,
  and then we'll add it in 4.2, or come up with a better solution.
 
  OK. I'm not applying it then.
 
 @arnd: I will send the patch in the next merge window then. Do you
 want me to do anything else for this merge window (e.g. resend the
 pull request without the patch)?

I am still applying my reversion patch to the arm-soc tree merge ...

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au


pgp2iSARRW5w8.pgp
Description: OpenPGP digital signature

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

[Matthias Brugger]

2015-04-08 16:49 GMT+02:00 Linus Walleij :
> On Tue, Apr 7, 2015 at 2:28 PM, Arnd Bergmann  wrote:
>> On Tuesday 07 April 2015 11:28:22 Linus Walleij wrote:
>>> On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
>>>  wrote:
>>> > 2015-04-07 3:12 GMT+02:00 Stephen Rothwell :
>>> >> Hi all,
>>> >>
>>> >> After merging the arm-soc tree, today's linux-next build (arm
>>> >> multi_v7_defconfig) failed like this:
>>> >>
>>> >> In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
>>> >>  from arch/arm/boot/dts/mt8135-evbp1.dts:16:
>>> >> arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
>>> >> dt-bindings/pinctrl/mt65xx.h: No such file or directory
>>> >>  #include 
>>> >> ^
>>> >>
>>> >> Caused by commit e6f219b8ec5e ("ARM: dts: mt8135: Add pinctrl/GPIO/EINT
>>> >> node for mt8135").
>>> >
>>> > This will be fixed as soon as Linus pinctrl for-next branch got merged 
>>> > [1].
>>>
>>> Hm that's unfortunate, we do not rely on merge orders.
>>>
>>> Either the ARM SoC tree needs to pull in the pinctrl commit
>>> or I need to carry this patch in the pinctrl tree.
>>>
>>> Is this sufficiently stand-alone to be merged into my tree
>>> or do you need to go by the former approach?
>>
>> Let's just delay this patch to another merge window. You can add the
>> driver now, and we should just revert the DT node addition in arm-soc,
>> and then we'll add it in 4.2, or come up with a better solution.
>
> OK. I'm not applying it then.

@arnd: I will send the patch in the next merge window then. Do you
want me to do anything else for this merge window (e.g. resend the
pull request without the patch)?

Cheers,
Matthias

-- 
motzblog.wordpress.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Linus Walleij]

On Tue, Apr 7, 2015 at 2:28 PM, Arnd Bergmann  wrote:
> On Tuesday 07 April 2015 11:28:22 Linus Walleij wrote:
>> On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
>>  wrote:
>> > 2015-04-07 3:12 GMT+02:00 Stephen Rothwell :
>> >> Hi all,
>> >>
>> >> After merging the arm-soc tree, today's linux-next build (arm
>> >> multi_v7_defconfig) failed like this:
>> >>
>> >> In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
>> >>  from arch/arm/boot/dts/mt8135-evbp1.dts:16:
>> >> arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
>> >> dt-bindings/pinctrl/mt65xx.h: No such file or directory
>> >>  #include 
>> >> ^
>> >>
>> >> Caused by commit e6f219b8ec5e ("ARM: dts: mt8135: Add pinctrl/GPIO/EINT
>> >> node for mt8135").
>> >
>> > This will be fixed as soon as Linus pinctrl for-next branch got merged [1].
>>
>> Hm that's unfortunate, we do not rely on merge orders.
>>
>> Either the ARM SoC tree needs to pull in the pinctrl commit
>> or I need to carry this patch in the pinctrl tree.
>>
>> Is this sufficiently stand-alone to be merged into my tree
>> or do you need to go by the former approach?
>
> Let's just delay this patch to another merge window. You can add the
> driver now, and we should just revert the DT node addition in arm-soc,
> and then we'll add it in 4.2, or come up with a better solution.

OK. I'm not applying it then.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Matthias Brugger]

2015-04-08 16:49 GMT+02:00 Linus Walleij linus.wall...@linaro.org:
 On Tue, Apr 7, 2015 at 2:28 PM, Arnd Bergmann a...@arndb.de wrote:
 On Tuesday 07 April 2015 11:28:22 Linus Walleij wrote:
 On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
 matthias@gmail.com wrote:
  2015-04-07 3:12 GMT+02:00 Stephen Rothwell s...@canb.auug.org.au:
  Hi all,
 
  After merging the arm-soc tree, today's linux-next build (arm
  multi_v7_defconfig) failed like this:
 
  In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
   from arch/arm/boot/dts/mt8135-evbp1.dts:16:
  arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
  dt-bindings/pinctrl/mt65xx.h: No such file or directory
   #include dt-bindings/pinctrl/mt65xx.h
  ^
 
  Caused by commit e6f219b8ec5e (ARM: dts: mt8135: Add pinctrl/GPIO/EINT
  node for mt8135).
 
  This will be fixed as soon as Linus pinctrl for-next branch got merged 
  [1].

 Hm that's unfortunate, we do not rely on merge orders.

 Either the ARM SoC tree needs to pull in the pinctrl commit
 or I need to carry this patch in the pinctrl tree.

 Is this sufficiently stand-alone to be merged into my tree
 or do you need to go by the former approach?

 Let's just delay this patch to another merge window. You can add the
 driver now, and we should just revert the DT node addition in arm-soc,
 and then we'll add it in 4.2, or come up with a better solution.

 OK. I'm not applying it then.

@arnd: I will send the patch in the next merge window then. Do you
want me to do anything else for this merge window (e.g. resend the
pull request without the patch)?

Cheers,
Matthias

-- 
motzblog.wordpress.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Linus Walleij]

On Tue, Apr 7, 2015 at 2:28 PM, Arnd Bergmann a...@arndb.de wrote:
 On Tuesday 07 April 2015 11:28:22 Linus Walleij wrote:
 On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
 matthias@gmail.com wrote:
  2015-04-07 3:12 GMT+02:00 Stephen Rothwell s...@canb.auug.org.au:
  Hi all,
 
  After merging the arm-soc tree, today's linux-next build (arm
  multi_v7_defconfig) failed like this:
 
  In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
   from arch/arm/boot/dts/mt8135-evbp1.dts:16:
  arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
  dt-bindings/pinctrl/mt65xx.h: No such file or directory
   #include dt-bindings/pinctrl/mt65xx.h
  ^
 
  Caused by commit e6f219b8ec5e (ARM: dts: mt8135: Add pinctrl/GPIO/EINT
  node for mt8135).
 
  This will be fixed as soon as Linus pinctrl for-next branch got merged [1].

 Hm that's unfortunate, we do not rely on merge orders.

 Either the ARM SoC tree needs to pull in the pinctrl commit
 or I need to carry this patch in the pinctrl tree.

 Is this sufficiently stand-alone to be merged into my tree
 or do you need to go by the former approach?

 Let's just delay this patch to another merge window. You can add the
 driver now, and we should just revert the DT node addition in arm-soc,
 and then we'll add it in 4.2, or come up with a better solution.

OK. I'm not applying it then.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Arnd Bergmann]

On Tuesday 07 April 2015 11:28:22 Linus Walleij wrote:
> On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
>  wrote:
> > 2015-04-07 3:12 GMT+02:00 Stephen Rothwell :
> >> Hi all,
> >>
> >> After merging the arm-soc tree, today's linux-next build (arm
> >> multi_v7_defconfig) failed like this:
> >>
> >> In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
> >>  from arch/arm/boot/dts/mt8135-evbp1.dts:16:
> >> arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
> >> dt-bindings/pinctrl/mt65xx.h: No such file or directory
> >>  #include 
> >> ^
> >>
> >> Caused by commit e6f219b8ec5e ("ARM: dts: mt8135: Add pinctrl/GPIO/EINT
> >> node for mt8135").
> >
> > This will be fixed as soon as Linus pinctrl for-next branch got merged [1].
> 
> Hm that's unfortunate, we do not rely on merge orders.
> 
> Either the ARM SoC tree needs to pull in the pinctrl commit
> or I need to carry this patch in the pinctrl tree.
> 
> Is this sufficiently stand-alone to be merged into my tree
> or do you need to go by the former approach?

Let's just delay this patch to another merge window. You can add the
driver now, and we should just revert the DT node addition in arm-soc,
and then we'll add it in 4.2, or come up with a better solution.

It's possible that we can come up with a way to avoid defining macros
for the pinctrl tables here.

Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Matthias Brugger]

2015-04-07 11:28 GMT+02:00 Linus Walleij :
> On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
>  wrote:
>> 2015-04-07 3:12 GMT+02:00 Stephen Rothwell :
>>> Hi all,
>>>
>>> After merging the arm-soc tree, today's linux-next build (arm
>>> multi_v7_defconfig) failed like this:
>>>
>>> In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
>>>  from arch/arm/boot/dts/mt8135-evbp1.dts:16:
>>> arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
>>> dt-bindings/pinctrl/mt65xx.h: No such file or directory
>>>  #include 
>>> ^
>>>
>>> Caused by commit e6f219b8ec5e ("ARM: dts: mt8135: Add pinctrl/GPIO/EINT
>>> node for mt8135").
>>
>> This will be fixed as soon as Linus pinctrl for-next branch got merged [1].
>
> Hm that's unfortunate, we do not rely on merge orders.
>
> Either the ARM SoC tree needs to pull in the pinctrl commit
> or I need to carry this patch in the pinctrl tree.
>
> Is this sufficiently stand-alone to be merged into my tree
> or do you need to go by the former approach?

It's a standalone patch, so for me it is fine if you merge the patch
into your tree.

Thanks,
Matthias

-- 
motzblog.wordpress.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Linus Walleij]

On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
 wrote:
> 2015-04-07 3:12 GMT+02:00 Stephen Rothwell :
>> Hi all,
>>
>> After merging the arm-soc tree, today's linux-next build (arm
>> multi_v7_defconfig) failed like this:
>>
>> In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
>>  from arch/arm/boot/dts/mt8135-evbp1.dts:16:
>> arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
>> dt-bindings/pinctrl/mt65xx.h: No such file or directory
>>  #include 
>> ^
>>
>> Caused by commit e6f219b8ec5e ("ARM: dts: mt8135: Add pinctrl/GPIO/EINT
>> node for mt8135").
>
> This will be fixed as soon as Linus pinctrl for-next branch got merged [1].

Hm that's unfortunate, we do not rely on merge orders.

Either the ARM SoC tree needs to pull in the pinctrl commit
or I need to carry this patch in the pinctrl tree.

Is this sufficiently stand-alone to be merged into my tree
or do you need to go by the former approach?

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Matthias Brugger]

2015-04-07 3:12 GMT+02:00 Stephen Rothwell :
> Hi all,
>
> After merging the arm-soc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
>  from arch/arm/boot/dts/mt8135-evbp1.dts:16:
> arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
> dt-bindings/pinctrl/mt65xx.h: No such file or directory
>  #include 
> ^
>
> Caused by commit e6f219b8ec5e ("ARM: dts: mt8135: Add pinctrl/GPIO/EINT
> node for mt8135").

This will be fixed as soon as Linus pinctrl for-next branch got merged [1].

Cheers,
Matthias

[1] 
https://git.kernel.org/cgit/linux/kernel/git/linusw/linux-pinctrl.git/commit/?h=for-next=a6df410d420aa4ff316797d352f69e7ebae5ff98

>
> I have reverted that commit for today.
> --
> Cheers,
> Stephen Rothwells...@canb.auug.org.au



-- 
motzblog.wordpress.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Matthias Brugger]

2015-04-07 3:12 GMT+02:00 Stephen Rothwell s...@canb.auug.org.au:
 Hi all,

 After merging the arm-soc tree, today's linux-next build (arm
 multi_v7_defconfig) failed like this:

 In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
  from arch/arm/boot/dts/mt8135-evbp1.dts:16:
 arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
 dt-bindings/pinctrl/mt65xx.h: No such file or directory
  #include dt-bindings/pinctrl/mt65xx.h
 ^

 Caused by commit e6f219b8ec5e (ARM: dts: mt8135: Add pinctrl/GPIO/EINT
 node for mt8135).

This will be fixed as soon as Linus pinctrl for-next branch got merged [1].

Cheers,
Matthias

[1] 
https://git.kernel.org/cgit/linux/kernel/git/linusw/linux-pinctrl.git/commit/?h=for-nextid=a6df410d420aa4ff316797d352f69e7ebae5ff98


 I have reverted that commit for today.
 --
 Cheers,
 Stephen Rothwells...@canb.auug.org.au



-- 
motzblog.wordpress.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Linus Walleij]

On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
matthias@gmail.com wrote:
 2015-04-07 3:12 GMT+02:00 Stephen Rothwell s...@canb.auug.org.au:
 Hi all,

 After merging the arm-soc tree, today's linux-next build (arm
 multi_v7_defconfig) failed like this:

 In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
  from arch/arm/boot/dts/mt8135-evbp1.dts:16:
 arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
 dt-bindings/pinctrl/mt65xx.h: No such file or directory
  #include dt-bindings/pinctrl/mt65xx.h
 ^

 Caused by commit e6f219b8ec5e (ARM: dts: mt8135: Add pinctrl/GPIO/EINT
 node for mt8135).

 This will be fixed as soon as Linus pinctrl for-next branch got merged [1].

Hm that's unfortunate, we do not rely on merge orders.

Either the ARM SoC tree needs to pull in the pinctrl commit
or I need to carry this patch in the pinctrl tree.

Is this sufficiently stand-alone to be merged into my tree
or do you need to go by the former approach?

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Matthias Brugger]

2015-04-07 11:28 GMT+02:00 Linus Walleij linus.wall...@linaro.org:
 On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
 matthias@gmail.com wrote:
 2015-04-07 3:12 GMT+02:00 Stephen Rothwell s...@canb.auug.org.au:
 Hi all,

 After merging the arm-soc tree, today's linux-next build (arm
 multi_v7_defconfig) failed like this:

 In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
  from arch/arm/boot/dts/mt8135-evbp1.dts:16:
 arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
 dt-bindings/pinctrl/mt65xx.h: No such file or directory
  #include dt-bindings/pinctrl/mt65xx.h
 ^

 Caused by commit e6f219b8ec5e (ARM: dts: mt8135: Add pinctrl/GPIO/EINT
 node for mt8135).

 This will be fixed as soon as Linus pinctrl for-next branch got merged [1].

 Hm that's unfortunate, we do not rely on merge orders.

 Either the ARM SoC tree needs to pull in the pinctrl commit
 or I need to carry this patch in the pinctrl tree.

 Is this sufficiently stand-alone to be merged into my tree
 or do you need to go by the former approach?

It's a standalone patch, so for me it is fine if you merge the patch
into your tree.

Thanks,
Matthias

-- 
motzblog.wordpress.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Arnd Bergmann]

On Tuesday 07 April 2015 11:28:22 Linus Walleij wrote:
 On Tue, Apr 7, 2015 at 10:43 AM, Matthias Brugger
 matthias@gmail.com wrote:
  2015-04-07 3:12 GMT+02:00 Stephen Rothwell s...@canb.auug.org.au:
  Hi all,
 
  After merging the arm-soc tree, today's linux-next build (arm
  multi_v7_defconfig) failed like this:
 
  In file included from arch/arm/boot/dts/mt8135.dtsi:18:0,
   from arch/arm/boot/dts/mt8135-evbp1.dts:16:
  arch/arm/boot/dts/mt8135-pinfunc.h:18:40: fatal error: 
  dt-bindings/pinctrl/mt65xx.h: No such file or directory
   #include dt-bindings/pinctrl/mt65xx.h
  ^
 
  Caused by commit e6f219b8ec5e (ARM: dts: mt8135: Add pinctrl/GPIO/EINT
  node for mt8135).
 
  This will be fixed as soon as Linus pinctrl for-next branch got merged [1].
 
 Hm that's unfortunate, we do not rely on merge orders.
 
 Either the ARM SoC tree needs to pull in the pinctrl commit
 or I need to carry this patch in the pinctrl tree.
 
 Is this sufficiently stand-alone to be merged into my tree
 or do you need to go by the former approach?

Let's just delay this patch to another merge window. You can add the
driver now, and we should just revert the DT node addition in arm-soc,
and then we'll add it in 4.2, or come up with a better solution.

It's possible that we can come up with a way to avoid defining macros
for the pinctrl tables here.

Arnd
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Javier Martinez Canillas]

Hello Russell,

On 10/03/2014 09:56 AM, Russell King - ARM Linux wrote:
> On Fri, Oct 03, 2014 at 08:50:09AM +0200, Javier Martinez Canillas wrote:
>> Hello Arnd, Stephen,
>> 
>> I'm so sorry about the breakage, when I posted this patch I mentioned that
>> it was meant for the 3.18-rc cycle once 3.18-rc1 was released [0]. Because
>> it fixes a regression caused by a patch queued in the clock tree for 3.18.
>> I should had been more explicit about the dependencies to avoid confusions.
> 
> If a patch is known to cause a regression, it shouldn't be going in during
> the merge window _or_ the fix patch should also go in during the merge
> window via the same route to resolve the regression before it's noticable.
> 
> Given the number of changes which go in during the merge window, waiting
> for -rc to fix a known bug *before* the merge window is not on - it breaks
> the ability to bisect during the period where bisect really is needed.
> 

I'm not the author of the patch that caused the regression, I just was bitten
by it and proposed a fix. So please don't kill the messenger :-)

Sorry, I didn't know about this rule, otherwise I would had asked Mike to pick
the fix instead. Or at least ask Kukjin to provide an immutable branch so Mike
could merge it on his clock tree.

Best regards,
Javier
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Russell King - ARM Linux]

On Fri, Oct 03, 2014 at 08:50:09AM +0200, Javier Martinez Canillas wrote:
> Hello Arnd, Stephen,
> 
> I'm so sorry about the breakage, when I posted this patch I mentioned that
> it was meant for the 3.18-rc cycle once 3.18-rc1 was released [0]. Because
> it fixes a regression caused by a patch queued in the clock tree for 3.18.
> I should had been more explicit about the dependencies to avoid confusions.

If a patch is known to cause a regression, it shouldn't be going in during
the merge window _or_ the fix patch should also go in during the merge
window via the same route to resolve the regression before it's noticable.

Given the number of changes which go in during the merge window, waiting
for -rc to fix a known bug *before* the merge window is not on - it breaks
the ability to bisect during the period where bisect really is needed.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Javier Martinez Canillas]

Hello Arnd, Stephen,

On 10/02/2014 04:32 PM, Arnd Bergmann wrote:
> On Thursday 02 October 2014 11:37:42 Stephen Rothwell wrote:
>> After merging the arm-soc tree, today's linux-next build (arm
>> multi_v7_defconfig) failed like this:
>> 
>> arch/arm/boot/dts/exynos5250-snow.dts:13:46: fatal error: 
>> dt-bindings/clock/maxim,max77686.h: No such file or directory
>>  #include 
>>   ^
>> 
>> Caused by commit c04c92ed5614 ("ARM: dts: Add rtc_src clk for s3c-rtc
>> on exynos5250-snow").
>> 
>> Presumably there is some dependency on some tree that someone has
>> forgotten to merge 
>> 
>> I reverted that commit for today.
>> 
>> Which then got to:
>> 
>> /scratch/sfr/next/arch/arm/boot/dts/exynos5420-peach-pit.dts:15:46: fatal 
>> error: dt-bindings/clock/maxim,max77802.h: No such file or directory
>>  #include 
>>   ^
>> compilation terminated.
>> /scratch/sfr/next/arch/arm/boot/dts/exynos5800-peach-pi.dts:15:46: fatal 
>> error: dt-bindings/clock/maxim,max77802.h: No such file or directory
>>  #include 
>>   ^
>> compilation terminated.
>> Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:417.21-22 syntax 
>> error
>> FATAL ERROR: Unable to parse input tree
>> 
>> Caused by 8bd43b6e6df7 ("ARM: dts: Add rtc_src clk for s3c-rtc on
>> exynos Peach boards").
>> 
>> I give up ... please test your trees better ...
> 
> I'm deeply sorry about that. I actually saw the problem here but was too
> tired to fix it up again by redoing all the merges in our next/late
> branch.
> 

I'm so sorry about the breakage, when I posted this patch I mentioned that
it was meant for the 3.18-rc cycle once 3.18-rc1 was released [0]. Because
it fixes a regression caused by a patch queued in the clock tree for 3.18.
I should had been more explicit about the dependencies to avoid confusions.

> I've changed the for-next branch now to drop all of next/late, I think
> we're better off not sending any of it for 3.18, especially as I found
> some other problems as well.
> 

Do you think that it may be possible to send this for the 3.18-rc cycle
or should it have to wait for 3.19? Without this the real time clock does
not work on the Peach Chromebooks and your next/late branch contains other
fixes as well (e.g: the Exynos USB dr_mode DT patches).

>> I have used the arm-soc tree form next-20141001 for today (which still
>> needs 5 reverts to get it to build :-().
> 
> D'oh. I actually fixed these already last friday in the next/dt branch
> but for some reason forgot to include it in for-next.
> I've made sure that everything is included now.
> 
>   Arnd
>

Thanks a lot and best regards,
Javier

[0]: 
https://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg36702.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Javier Martinez Canillas]

Hello Arnd, Stephen,

On 10/02/2014 04:32 PM, Arnd Bergmann wrote:
 On Thursday 02 October 2014 11:37:42 Stephen Rothwell wrote:
 After merging the arm-soc tree, today's linux-next build (arm
 multi_v7_defconfig) failed like this:
 
 arch/arm/boot/dts/exynos5250-snow.dts:13:46: fatal error: 
 dt-bindings/clock/maxim,max77686.h: No such file or directory
  #include dt-bindings/clock/maxim,max77686.h
   ^
 
 Caused by commit c04c92ed5614 (ARM: dts: Add rtc_src clk for s3c-rtc
 on exynos5250-snow).
 
 Presumably there is some dependency on some tree that someone has
 forgotten to merge 
 
 I reverted that commit for today.
 
 Which then got to:
 
 /scratch/sfr/next/arch/arm/boot/dts/exynos5420-peach-pit.dts:15:46: fatal 
 error: dt-bindings/clock/maxim,max77802.h: No such file or directory
  #include dt-bindings/clock/maxim,max77802.h
   ^
 compilation terminated.
 /scratch/sfr/next/arch/arm/boot/dts/exynos5800-peach-pi.dts:15:46: fatal 
 error: dt-bindings/clock/maxim,max77802.h: No such file or directory
  #include dt-bindings/clock/maxim,max77802.h
   ^
 compilation terminated.
 Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:417.21-22 syntax 
 error
 FATAL ERROR: Unable to parse input tree
 
 Caused by 8bd43b6e6df7 (ARM: dts: Add rtc_src clk for s3c-rtc on
 exynos Peach boards).
 
 I give up ... please test your trees better ...
 
 I'm deeply sorry about that. I actually saw the problem here but was too
 tired to fix it up again by redoing all the merges in our next/late
 branch.
 

I'm so sorry about the breakage, when I posted this patch I mentioned that
it was meant for the 3.18-rc cycle once 3.18-rc1 was released [0]. Because
it fixes a regression caused by a patch queued in the clock tree for 3.18.
I should had been more explicit about the dependencies to avoid confusions.

 I've changed the for-next branch now to drop all of next/late, I think
 we're better off not sending any of it for 3.18, especially as I found
 some other problems as well.
 

Do you think that it may be possible to send this for the 3.18-rc cycle
or should it have to wait for 3.19? Without this the real time clock does
not work on the Peach Chromebooks and your next/late branch contains other
fixes as well (e.g: the Exynos USB dr_mode DT patches).

 I have used the arm-soc tree form next-20141001 for today (which still
 needs 5 reverts to get it to build :-().
 
 D'oh. I actually fixed these already last friday in the next/dt branch
 but for some reason forgot to include it in for-next.
 I've made sure that everything is included now.
 
   Arnd


Thanks a lot and best regards,
Javier

[0]: 
https://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg36702.html
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Russell King - ARM Linux]

On Fri, Oct 03, 2014 at 08:50:09AM +0200, Javier Martinez Canillas wrote:
 Hello Arnd, Stephen,
 
 I'm so sorry about the breakage, when I posted this patch I mentioned that
 it was meant for the 3.18-rc cycle once 3.18-rc1 was released [0]. Because
 it fixes a regression caused by a patch queued in the clock tree for 3.18.
 I should had been more explicit about the dependencies to avoid confusions.

If a patch is known to cause a regression, it shouldn't be going in during
the merge window _or_ the fix patch should also go in during the merge
window via the same route to resolve the regression before it's noticable.

Given the number of changes which go in during the merge window, waiting
for -rc to fix a known bug *before* the merge window is not on - it breaks
the ability to bisect during the period where bisect really is needed.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Javier Martinez Canillas]

Hello Russell,

On 10/03/2014 09:56 AM, Russell King - ARM Linux wrote:
 On Fri, Oct 03, 2014 at 08:50:09AM +0200, Javier Martinez Canillas wrote:
 Hello Arnd, Stephen,
 
 I'm so sorry about the breakage, when I posted this patch I mentioned that
 it was meant for the 3.18-rc cycle once 3.18-rc1 was released [0]. Because
 it fixes a regression caused by a patch queued in the clock tree for 3.18.
 I should had been more explicit about the dependencies to avoid confusions.
 
 If a patch is known to cause a regression, it shouldn't be going in during
 the merge window _or_ the fix patch should also go in during the merge
 window via the same route to resolve the regression before it's noticable.
 
 Given the number of changes which go in during the merge window, waiting
 for -rc to fix a known bug *before* the merge window is not on - it breaks
 the ability to bisect during the period where bisect really is needed.
 

I'm not the author of the patch that caused the regression, I just was bitten
by it and proposed a fix. So please don't kill the messenger :-)

Sorry, I didn't know about this rule, otherwise I would had asked Mike to pick
the fix instead. Or at least ask Kukjin to provide an immutable branch so Mike
could merge it on his clock tree.

Best regards,
Javier
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Arnd Bergmann]

On Thursday 02 October 2014 11:37:42 Stephen Rothwell wrote:
> After merging the arm-soc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> arch/arm/boot/dts/exynos5250-snow.dts:13:46: fatal error: 
> dt-bindings/clock/maxim,max77686.h: No such file or directory
>  #include 
>   ^
> 
> Caused by commit c04c92ed5614 ("ARM: dts: Add rtc_src clk for s3c-rtc
> on exynos5250-snow").
> 
> Presumably there is some dependency on some tree that someone has
> forgotten to merge 
> 
> I reverted that commit for today.
> 
> Which then got to:
> 
> /scratch/sfr/next/arch/arm/boot/dts/exynos5420-peach-pit.dts:15:46: fatal 
> error: dt-bindings/clock/maxim,max77802.h: No such file or directory
>  #include 
>   ^
> compilation terminated.
> /scratch/sfr/next/arch/arm/boot/dts/exynos5800-peach-pi.dts:15:46: fatal 
> error: dt-bindings/clock/maxim,max77802.h: No such file or directory
>  #include 
>   ^
> compilation terminated.
> Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:417.21-22 syntax 
> error
> FATAL ERROR: Unable to parse input tree
> 
> Caused by 8bd43b6e6df7 ("ARM: dts: Add rtc_src clk for s3c-rtc on
> exynos Peach boards").
> 
> I give up ... please test your trees better ...

I'm deeply sorry about that. I actually saw the problem here but was too
tired to fix it up again by redoing all the merges in our next/late
branch.

I've changed the for-next branch now to drop all of next/late, I think
we're better off not sending any of it for 3.18, especially as I found
some other problems as well.

> I have used the arm-soc tree form next-20141001 for today (which still
> needs 5 reverts to get it to build :-().

D'oh. I actually fixed these already last friday in the next/dt branch
but for some reason forgot to include it in for-next.
I've made sure that everything is included now.

Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Arnd Bergmann]

On Thursday 02 October 2014 11:37:42 Stephen Rothwell wrote:
 After merging the arm-soc tree, today's linux-next build (arm
 multi_v7_defconfig) failed like this:
 
 arch/arm/boot/dts/exynos5250-snow.dts:13:46: fatal error: 
 dt-bindings/clock/maxim,max77686.h: No such file or directory
  #include dt-bindings/clock/maxim,max77686.h
   ^
 
 Caused by commit c04c92ed5614 (ARM: dts: Add rtc_src clk for s3c-rtc
 on exynos5250-snow).
 
 Presumably there is some dependency on some tree that someone has
 forgotten to merge 
 
 I reverted that commit for today.
 
 Which then got to:
 
 /scratch/sfr/next/arch/arm/boot/dts/exynos5420-peach-pit.dts:15:46: fatal 
 error: dt-bindings/clock/maxim,max77802.h: No such file or directory
  #include dt-bindings/clock/maxim,max77802.h
   ^
 compilation terminated.
 /scratch/sfr/next/arch/arm/boot/dts/exynos5800-peach-pi.dts:15:46: fatal 
 error: dt-bindings/clock/maxim,max77802.h: No such file or directory
  #include dt-bindings/clock/maxim,max77802.h
   ^
 compilation terminated.
 Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:417.21-22 syntax 
 error
 FATAL ERROR: Unable to parse input tree
 
 Caused by 8bd43b6e6df7 (ARM: dts: Add rtc_src clk for s3c-rtc on
 exynos Peach boards).
 
 I give up ... please test your trees better ...

I'm deeply sorry about that. I actually saw the problem here but was too
tired to fix it up again by redoing all the merges in our next/late
branch.

I've changed the for-next branch now to drop all of next/late, I think
we're better off not sending any of it for 3.18, especially as I found
some other problems as well.

 I have used the arm-soc tree form next-20141001 for today (which still
 needs 5 reverts to get it to build :-().

D'oh. I actually fixed these already last friday in the next/dt branch
but for some reason forgot to include it in for-next.
I've made sure that everything is included now.

Arnd
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: linux-next: build failure after merge of the arm-soc tree

[Kukjin Kim]

+ Mike

Stephen Rothwell wrote:
> 
> Hi all,
> 
Hi,

> After merging the arm-soc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> arch/arm/boot/dts/exynos5250-snow.dts:13:46: fatal error: 
> dt-bindings/clock/maxim,max77686.h: No such
> file or directory
>  #include 
>   ^
> 
> Caused by commit c04c92ed5614 ("ARM: dts: Add rtc_src clk for s3c-rtc
> on exynos5250-snow").
> 
> Presumably there is some dependency on some tree that someone has
> forgotten to merge :-(
> 
Hmm...I thought it should be fine once Mike's clk tree is landing into the
-next tree. Firstly sorry about that and how should I do in this case?

> I reverted that commit for today.
> 
> Which then got to:
> 
> /scratch/sfr/next/arch/arm/boot/dts/exynos5420-peach-pit.dts:15:46: fatal 
> error: dt-
> bindings/clock/maxim,max77802.h: No such file or directory
>  #include 
>   ^
> compilation terminated.
> /scratch/sfr/next/arch/arm/boot/dts/exynos5800-peach-pi.dts:15:46: fatal 
> error: dt-
> bindings/clock/maxim,max77802.h: No such file or directory
>  #include 
>   ^
> compilation terminated.
> Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:417.21-22 syntax 
> error
> FATAL ERROR: Unable to parse input tree
> 
> Caused by 8bd43b6e6df7 ("ARM: dts: Add rtc_src clk for s3c-rtc on
> exynos Peach boards").
> 
> I give up ... please test your trees better ...
> 
So sorry, actually it's my fault, I missed the information to arm-soc when I
sent a pull-request, just I thought arm-soc were aware of that before happening
the error when samsung tree merged...

- Kukjin

> I have used the arm-soc tree form next-20141001 for today (which still
> needs 5 reverts to get it to build :-().

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: linux-next: build failure after merge of the arm-soc tree

[Kukjin Kim]

+ Mike

Stephen Rothwell wrote:
 
 Hi all,
 
Hi,

 After merging the arm-soc tree, today's linux-next build (arm
 multi_v7_defconfig) failed like this:
 
 arch/arm/boot/dts/exynos5250-snow.dts:13:46: fatal error: 
 dt-bindings/clock/maxim,max77686.h: No such
 file or directory
  #include dt-bindings/clock/maxim,max77686.h
   ^
 
 Caused by commit c04c92ed5614 (ARM: dts: Add rtc_src clk for s3c-rtc
 on exynos5250-snow).
 
 Presumably there is some dependency on some tree that someone has
 forgotten to merge :-(
 
Hmm...I thought it should be fine once Mike's clk tree is landing into the
-next tree. Firstly sorry about that and how should I do in this case?

 I reverted that commit for today.
 
 Which then got to:
 
 /scratch/sfr/next/arch/arm/boot/dts/exynos5420-peach-pit.dts:15:46: fatal 
 error: dt-
 bindings/clock/maxim,max77802.h: No such file or directory
  #include dt-bindings/clock/maxim,max77802.h
   ^
 compilation terminated.
 /scratch/sfr/next/arch/arm/boot/dts/exynos5800-peach-pi.dts:15:46: fatal 
 error: dt-
 bindings/clock/maxim,max77802.h: No such file or directory
  #include dt-bindings/clock/maxim,max77802.h
   ^
 compilation terminated.
 Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:417.21-22 syntax 
 error
 FATAL ERROR: Unable to parse input tree
 
 Caused by 8bd43b6e6df7 (ARM: dts: Add rtc_src clk for s3c-rtc on
 exynos Peach boards).
 
 I give up ... please test your trees better ...
 
So sorry, actually it's my fault, I missed the information to arm-soc when I
sent a pull-request, just I thought arm-soc were aware of that before happening
the error when samsung tree merged...

- Kukjin

 I have used the arm-soc tree form next-20141001 for today (which still
 needs 5 reverts to get it to build :-().

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Wei Xu]

On 2014/9/30 8:12, Stephen Rothwell wrote:
> Hi all,
> 
> On Fri, 26 Sep 2014 11:55:39 +1000 Stephen Rothwell  
> wrote:
>>
>> After merging the arm-soc tree, today's linux-next build (arm
>> multi_v7_defconfig) failed like this:
>>
>> Error: arch/arm/boot/dts/hisi-x5hd2.dtsi:374.22-23 syntax error
>> FATAL ERROR: Unable to parse input tree 
> OK, now I get:
> 
> Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:417.21-22 syntax 
> error
> FATAL ERROR: Unable to parse input tree
> Are you guys really testing this stuff? :-(

Hi Stephen, Olof, Arnd,

Sorry for my fault and bring so much trouble to all of you.
I sent this pull request before the clock patch set being accepted.
And I did forget to compile the dtb. 
But I will make sure it will *not* happen next time.
Arnd has already helped to revert the series of this patch set in 
arm-soc.git:next/dt.

Hi Arnd, Olof,

Could you please help to revert this series of patch set in 
arm-soc.git:for-next?
Thanks!

Best Regards,
Wei
 
>> There are a series of new commits to this file today and I have no idea
>> which one caused the problem.
>>
>> I reverted:
>>
>> 610bd8722ef4 "ARM: dts: hix5hd2: add wdg node"
> 
> Reverted in the arm-soc tree.
> 
>> 6868feb6dd97 "ARM: dts: hix5hd2: add gpio node"
> 
> Error is now:
> 
> Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:183.21-22 syntax 
> error
> 
>> 420a2d55f046 "ARM: dts: hix5hd2: add sata node"
> 
> Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:183.21-22 syntax 
> error
> 
> 
>> f16c7fb2f3ff "ARM: dts: hix5hd2: add usb node"
> 
> Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:183.21-22 syntax 
> error
> 
>> b196e1ca400d "ARM: dts: hix5hd2: add mmc node"
> 
> Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:174.21-22 syntax 
> error
> 
>> de8b6054780e "ARM: dts: hix5hd2: add gmac node"
> 
> no more errors.
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Stephen Rothwell]

Hi all,

On Fri, 26 Sep 2014 11:55:39 +1000 Stephen Rothwell  
wrote:
>
> After merging the arm-soc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> Error: arch/arm/boot/dts/hisi-x5hd2.dtsi:374.22-23 syntax error
> FATAL ERROR: Unable to parse input tree

OK, now I get:

Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:417.21-22 syntax 
error
FATAL ERROR: Unable to parse input tree

Are you guys really testing this stuff? :-(

> There are a series of new commits to this file today and I have no idea
> which one caused the problem.
> 
> I reverted:
> 
> 610bd8722ef4  "ARM: dts: hix5hd2: add wdg node"

Reverted in the arm-soc tree.

> 6868feb6dd97  "ARM: dts: hix5hd2: add gpio node"

Error is now:

Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:183.21-22 syntax 
error

> 420a2d55f046  "ARM: dts: hix5hd2: add sata node"

Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:183.21-22 syntax 
error


> f16c7fb2f3ff  "ARM: dts: hix5hd2: add usb node"

Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:183.21-22 syntax 
error

> b196e1ca400d  "ARM: dts: hix5hd2: add mmc node"

Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:174.21-22 syntax 
error

> de8b6054780e  "ARM: dts: hix5hd2: add gmac node"

no more errors.

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au


signature.asc
Description: PGP signature

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

[Stephen Rothwell]

Hi all,

On Fri, 26 Sep 2014 11:55:39 +1000 Stephen Rothwell s...@canb.auug.org.au 
wrote:

 After merging the arm-soc tree, today's linux-next build (arm
 multi_v7_defconfig) failed like this:
 
 Error: arch/arm/boot/dts/hisi-x5hd2.dtsi:374.22-23 syntax error
 FATAL ERROR: Unable to parse input tree

OK, now I get:

Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:417.21-22 syntax 
error
FATAL ERROR: Unable to parse input tree

Are you guys really testing this stuff? :-(

 There are a series of new commits to this file today and I have no idea
 which one caused the problem.
 
 I reverted:
 
 610bd8722ef4  ARM: dts: hix5hd2: add wdg node

Reverted in the arm-soc tree.

 6868feb6dd97  ARM: dts: hix5hd2: add gpio node

Error is now:

Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:183.21-22 syntax 
error

 420a2d55f046  ARM: dts: hix5hd2: add sata node

Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:183.21-22 syntax 
error


 f16c7fb2f3ff  ARM: dts: hix5hd2: add usb node

Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:183.21-22 syntax 
error

 b196e1ca400d  ARM: dts: hix5hd2: add mmc node

Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:174.21-22 syntax 
error

 de8b6054780e  ARM: dts: hix5hd2: add gmac node

no more errors.

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au


signature.asc
Description: PGP signature

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

[Wei Xu]

On 2014/9/30 8:12, Stephen Rothwell wrote:
 Hi all,
 
 On Fri, 26 Sep 2014 11:55:39 +1000 Stephen Rothwell s...@canb.auug.org.au 
 wrote:

 After merging the arm-soc tree, today's linux-next build (arm
 multi_v7_defconfig) failed like this:

 Error: arch/arm/boot/dts/hisi-x5hd2.dtsi:374.22-23 syntax error
 FATAL ERROR: Unable to parse input tree 
 OK, now I get:
 
 Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:417.21-22 syntax 
 error
 FATAL ERROR: Unable to parse input tree
 Are you guys really testing this stuff? :-(

Hi Stephen, Olof, Arnd,

Sorry for my fault and bring so much trouble to all of you.
I sent this pull request before the clock patch set being accepted.
And I did forget to compile the dtb. 
But I will make sure it will *not* happen next time.
Arnd has already helped to revert the series of this patch set in 
arm-soc.git:next/dt.

Hi Arnd, Olof,

Could you please help to revert this series of patch set in 
arm-soc.git:for-next?
Thanks!

Best Regards,
Wei
 
 There are a series of new commits to this file today and I have no idea
 which one caused the problem.

 I reverted:

 610bd8722ef4 ARM: dts: hix5hd2: add wdg node
 
 Reverted in the arm-soc tree.
 
 6868feb6dd97 ARM: dts: hix5hd2: add gpio node
 
 Error is now:
 
 Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:183.21-22 syntax 
 error
 
 420a2d55f046 ARM: dts: hix5hd2: add sata node
 
 Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:183.21-22 syntax 
 error
 
 
 f16c7fb2f3ff ARM: dts: hix5hd2: add usb node
 
 Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:183.21-22 syntax 
 error
 
 b196e1ca400d ARM: dts: hix5hd2: add mmc node
 
 Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:174.21-22 syntax 
 error
 
 de8b6054780e ARM: dts: hix5hd2: add gmac node
 
 no more errors.
 

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Wei Xu]

On 2014/9/26 9:55, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the arm-soc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> Error: arch/arm/boot/dts/hisi-x5hd2.dtsi:374.22-23 syntax error
> FATAL ERROR: Unable to parse input tree
> 
> There are a series of new commits to this file today and I have no idea
> which one caused the problem.

Hi Stephen,

Sorry for that.
It is caused by this commit: 610bd8722ef4 "ARM: dts: hix5hd2: add wdg node".
And Olof has already helped to reverted this commit.

Best Regards,
Wei

> I reverted:
> 
> 610bd8722ef4  "ARM: dts: hix5hd2: add wdg node"
> 6868feb6dd97  "ARM: dts: hix5hd2: add gpio node"
> 420a2d55f046  "ARM: dts: hix5hd2: add sata node"
> f16c7fb2f3ff  "ARM: dts: hix5hd2: add usb node"
> b196e1ca400d  "ARM: dts: hix5hd2: add mmc node"
> de8b6054780e  "ARM: dts: hix5hd2: add gmac node"
> 
> which fixed the build problem.
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Wei Xu]

On 2014/9/26 9:55, Stephen Rothwell wrote:
 Hi all,
 
 After merging the arm-soc tree, today's linux-next build (arm
 multi_v7_defconfig) failed like this:
 
 Error: arch/arm/boot/dts/hisi-x5hd2.dtsi:374.22-23 syntax error
 FATAL ERROR: Unable to parse input tree
 
 There are a series of new commits to this file today and I have no idea
 which one caused the problem.

Hi Stephen,

Sorry for that.
It is caused by this commit: 610bd8722ef4 ARM: dts: hix5hd2: add wdg node.
And Olof has already helped to reverted this commit.

Best Regards,
Wei

 I reverted:
 
 610bd8722ef4  ARM: dts: hix5hd2: add wdg node
 6868feb6dd97  ARM: dts: hix5hd2: add gpio node
 420a2d55f046  ARM: dts: hix5hd2: add sata node
 f16c7fb2f3ff  ARM: dts: hix5hd2: add usb node
 b196e1ca400d  ARM: dts: hix5hd2: add mmc node
 de8b6054780e  ARM: dts: hix5hd2: add gmac node
 
 which fixed the build problem.
 

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Catalin Marinas]

On Mon, Mar 10, 2014 at 10:45:58AM +, Will Deacon wrote:
> On Sun, Mar 09, 2014 at 11:55:14AM +, Mark Brown wrote:
> > Hi all,
> 
> Hi Mark,
> 
> > After merging the arm-soc tree, today's linux-next build (20140309)
> > failed for arm64 defconfig like this:
> > 
> > /home/broonie/next/next/drivers/irqchip/irq-gic.c: In function 
> > 'gic_raise_softirq':
> > /home/broonie/next/next/drivers/irqchip/irq-gic.c:666:2: error: implicit 
> > declaration of function 'dmb' [-Werror=implicit-function-declaration]
> >   dmb(ishst);
> >   ^
> 
> Damnit, that's because we ended up going with dmb instead of dsb after it
> (surprisingly) turned out to be sufficient. The simple patch below fixes the
> problem -- Catalin, can we get this into -next please?

Done.

-- 
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Will Deacon]

On Sun, Mar 09, 2014 at 11:55:14AM +, Mark Brown wrote:
> Hi all,

Hi Mark,

> After merging the arm-soc tree, today's linux-next build (20140309)
> failed for arm64 defconfig like this:
> 
> /home/broonie/next/next/drivers/irqchip/irq-gic.c: In function 
> 'gic_raise_softirq':
> /home/broonie/next/next/drivers/irqchip/irq-gic.c:666:2: error: implicit 
> declaration of function 'dmb' [-Werror=implicit-function-declaration]
>   dmb(ishst);
>   ^

Damnit, that's because we ended up going with dmb instead of dsb after it
(surprisingly) turned out to be sufficient. The simple patch below fixes the
problem -- Catalin, can we get this into -next please?

I have an extra patch which actually makes use of the options, but we should
get things building again first.

Cheers,

Will

--->8

>From bacbd4af61a671ad21f58197ed16116ff41b54cd Mon Sep 17 00:00:00 2001
From: Will Deacon 
Date: Mon, 10 Mar 2014 10:36:52 +
Subject: [PATCH] arm64: barriers: add dmb barrier

Commit 8adbf57fc429 ("irqchip: gic: use dmb ishst instead of dsb when
raising a softirq") added an explicit dmb(...) call to the GIC driver.

This patch adds a simple dmb() macro to arm64, which expands to a DMB SY
instruction.

Signed-off-by: Will Deacon 
---
 arch/arm64/include/asm/barrier.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm64/include/asm/barrier.h b/arch/arm64/include/asm/barrier.h
index 409ca370cfe2..66eb7648043b 100644
--- a/arch/arm64/include/asm/barrier.h
+++ b/arch/arm64/include/asm/barrier.h
@@ -25,6 +25,7 @@
 #define wfi()  asm volatile("wfi" : : : "memory")
 
 #define isb()  asm volatile("isb" : : : "memory")
+#define dmb(opt)   asm volatile("dmb sy" : : : "memory")
 #define dsb(opt)   asm volatile("dsb sy" : : : "memory")
 
 #define mb()   dsb()
-- 
1.8.2.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Will Deacon]

On Sun, Mar 09, 2014 at 11:55:14AM +, Mark Brown wrote:
 Hi all,

Hi Mark,

 After merging the arm-soc tree, today's linux-next build (20140309)
 failed for arm64 defconfig like this:
 
 /home/broonie/next/next/drivers/irqchip/irq-gic.c: In function 
 'gic_raise_softirq':
 /home/broonie/next/next/drivers/irqchip/irq-gic.c:666:2: error: implicit 
 declaration of function 'dmb' [-Werror=implicit-function-declaration]
   dmb(ishst);
   ^

Damnit, that's because we ended up going with dmb instead of dsb after it
(surprisingly) turned out to be sufficient. The simple patch below fixes the
problem -- Catalin, can we get this into -next please?

I have an extra patch which actually makes use of the options, but we should
get things building again first.

Cheers,

Will

---8

From bacbd4af61a671ad21f58197ed16116ff41b54cd Mon Sep 17 00:00:00 2001
From: Will Deacon will.dea...@arm.com
Date: Mon, 10 Mar 2014 10:36:52 +
Subject: [PATCH] arm64: barriers: add dmb barrier

Commit 8adbf57fc429 (irqchip: gic: use dmb ishst instead of dsb when
raising a softirq) added an explicit dmb(...) call to the GIC driver.

This patch adds a simple dmb() macro to arm64, which expands to a DMB SY
instruction.

Signed-off-by: Will Deacon will.dea...@arm.com
---
 arch/arm64/include/asm/barrier.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm64/include/asm/barrier.h b/arch/arm64/include/asm/barrier.h
index 409ca370cfe2..66eb7648043b 100644
--- a/arch/arm64/include/asm/barrier.h
+++ b/arch/arm64/include/asm/barrier.h
@@ -25,6 +25,7 @@
 #define wfi()  asm volatile(wfi : : : memory)
 
 #define isb()  asm volatile(isb : : : memory)
+#define dmb(opt)   asm volatile(dmb sy : : : memory)
 #define dsb(opt)   asm volatile(dsb sy : : : memory)
 
 #define mb()   dsb()
-- 
1.8.2.2
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Catalin Marinas]

On Mon, Mar 10, 2014 at 10:45:58AM +, Will Deacon wrote:
 On Sun, Mar 09, 2014 at 11:55:14AM +, Mark Brown wrote:
  Hi all,
 
 Hi Mark,
 
  After merging the arm-soc tree, today's linux-next build (20140309)
  failed for arm64 defconfig like this:
  
  /home/broonie/next/next/drivers/irqchip/irq-gic.c: In function 
  'gic_raise_softirq':
  /home/broonie/next/next/drivers/irqchip/irq-gic.c:666:2: error: implicit 
  declaration of function 'dmb' [-Werror=implicit-function-declaration]
dmb(ishst);
^
 
 Damnit, that's because we ended up going with dmb instead of dsb after it
 (surprisingly) turned out to be sufficient. The simple patch below fixes the
 problem -- Catalin, can we get this into -next please?

Done.

-- 
Catalin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Mark Brown]

On Sun, Mar 09, 2014 at 10:08:58AM -0700, Olof Johansson wrote:
> On Sun, Mar 9, 2014 at 4:41 AM, Mark Brown  wrote:

> > ERROR: Input tree has errors, aborting (use -f to force output)
> > make[2]: *** [arch/arm/boot/dts/socfpga_arria5_socdk.dtb] Error 2

> Known issue, I unmerged the offending branch but didn't push out the
> backed out for-next branch last night (I was unaware that you were
> doing linux-next now, and sfr doesn't do them until Sunday night our
> time, so I didn't think it was urgent).

No worries, I wouldn't have done it on a Sunday either but this time
round I've got Stephen's scripts so I've been pipe cleaning those so
hopefully everything will actually run properly on Monday.


signature.asc
Description: Digital signature

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

[Olof Johansson]

On Sun, Mar 9, 2014 at 4:41 AM, Mark Brown  wrote:
> Hi all,
>
> After merging the arm-soc tree, today's linux-next build (20140309)
> failed for multi_v7_defconfig like this:
>
> ERROR (phandle_references): Reference to non-existent node or label "sysmgr"
>
> ERROR (phandle_references): Reference to non-existent node or label "sysmgr"
>
> ERROR: Input tree has errors, aborting (use -f to force output)
> make[2]: *** [arch/arm/boot/dts/socfpga_arria5_socdk.dtb] Error 2

Known issue, I unmerged the offending branch but didn't push out the
backed out for-next branch last night (I was unaware that you were
doing linux-next now, and sfr doesn't do them until Sunday night our
time, so I didn't think it was urgent).



-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Olof Johansson]

On Sun, Mar 9, 2014 at 4:41 AM, Mark Brown broo...@kernel.org wrote:
 Hi all,

 After merging the arm-soc tree, today's linux-next build (20140309)
 failed for multi_v7_defconfig like this:

 ERROR (phandle_references): Reference to non-existent node or label sysmgr

 ERROR (phandle_references): Reference to non-existent node or label sysmgr

 ERROR: Input tree has errors, aborting (use -f to force output)
 make[2]: *** [arch/arm/boot/dts/socfpga_arria5_socdk.dtb] Error 2

Known issue, I unmerged the offending branch but didn't push out the
backed out for-next branch last night (I was unaware that you were
doing linux-next now, and sfr doesn't do them until Sunday night our
time, so I didn't think it was urgent).



-Olof
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Mark Brown]

On Sun, Mar 09, 2014 at 10:08:58AM -0700, Olof Johansson wrote:
 On Sun, Mar 9, 2014 at 4:41 AM, Mark Brown broo...@kernel.org wrote:

  ERROR: Input tree has errors, aborting (use -f to force output)
  make[2]: *** [arch/arm/boot/dts/socfpga_arria5_socdk.dtb] Error 2

 Known issue, I unmerged the offending branch but didn't push out the
 backed out for-next branch last night (I was unaware that you were
 doing linux-next now, and sfr doesn't do them until Sunday night our
 time, so I didn't think it was urgent).

No worries, I wouldn't have done it on a Sunday either but this time
round I've got Stephen's scripts so I've been pipe cleaning those so
hopefully everything will actually run properly on Monday.


signature.asc
Description: Digital signature

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

[Thomas Petazzoni]

Dear Olof Johansson,

On Fri, 19 Apr 2013 07:01:28 -0700, Olof Johansson wrote:

> > After merging the arm-soc tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > powerpc64-linux-ld: cannot find drivers/pci/host/built-in.o: No
> > such file or directory
> >
> > Caused by commit 9ecbe03ae85b ("pci: infrastructure to add drivers
> > in drivers/pci/host").
> >
> > I have used the arm-soc tree from next-20130418 for today.
> 
> Sorry about that, I'll drop the branch that brought in the of_pci
> consolidation from our repo.

The build failure reported here is totally independent of the of_pci
consolidation work. It's caused by the commit pointed in this e-mail,
and it is independent from Andrew Murray's work on of_pci consolidation.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Thomas Petazzoni]

Dear Olof Johansson,

On Fri, 19 Apr 2013 07:01:28 -0700, Olof Johansson wrote:

  After merging the arm-soc tree, today's linux-next build (powerpc
  ppc64_defconfig) failed like this:
 
  powerpc64-linux-ld: cannot find drivers/pci/host/built-in.o: No
  such file or directory
 
  Caused by commit 9ecbe03ae85b (pci: infrastructure to add drivers
  in drivers/pci/host).
 
  I have used the arm-soc tree from next-20130418 for today.
 
 Sorry about that, I'll drop the branch that brought in the of_pci
 consolidation from our repo.

The build failure reported here is totally independent of the of_pci
consolidation work. It's caused by the commit pointed in this e-mail,
and it is independent from Andrew Murray's work on of_pci consolidation.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Olof Johansson]

On Thu, Apr 18, 2013 at 11:46 PM, Stephen Rothwell  
wrote:
> Hi all,
>
> After merging the arm-soc tree, today's linux-next build (powerpc 
> ppc64_defconfig)
> failed like this:
>
> powerpc64-linux-ld: cannot find drivers/pci/host/built-in.o: No such file or 
> directory
>
> Caused by commit 9ecbe03ae85b ("pci: infrastructure to add drivers in
> drivers/pci/host").
>
> I have used the arm-soc tree from next-20130418 for today.

Sorry about that, I'll drop the branch that brought in the of_pci
consolidation from our repo.


-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

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

[Olof Johansson]

On Thu, Apr 18, 2013 at 11:46 PM, Stephen Rothwell s...@canb.auug.org.au 
wrote:
 Hi all,

 After merging the arm-soc tree, today's linux-next build (powerpc 
 ppc64_defconfig)
 failed like this:

 powerpc64-linux-ld: cannot find drivers/pci/host/built-in.o: No such file or 
 directory

 Caused by commit 9ecbe03ae85b (pci: infrastructure to add drivers in
 drivers/pci/host).

 I have used the arm-soc tree from next-20130418 for today.

Sorry about that, I'll drop the branch that brought in the of_pci
consolidation from our repo.


-Olof
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/