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

On 22/04/2017 01:43, Russell King - ARM Linux wrote: > On Fri, Apr 21, 2017 at 06:12:30PM +1000, Stephen Rothwell wrote: >> Hi Mason, >> >> On Fri, 21 Apr 2017 09:58:58 +0200 Mason wrote: >>> >>> Anyway, the fix is trivial. >>> >>> The "pchans_used" field is an unsigned long

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

On 22/04/2017 01:43, Russell King - ARM Linux wrote: > On Fri, Apr 21, 2017 at 06:12:30PM +1000, Stephen Rothwell wrote: >> Hi Mason, >> >> On Fri, 21 Apr 2017 09:58:58 +0200 Mason wrote: >>> >>> Anyway, the fix is trivial. >>> >>> The "pchans_used" field is an unsigned long array. >>>

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

On Sat, Apr 22, 2017 at 10:41:37AM +0200, Mason wrote: > On 22/04/2017 01:43, Russell King - ARM Linux wrote: > > > Or I drop the offending patch (done) and we get the DMA subsystem fixed > > first. Given how long it's been this way, I doubt there's any hurry to > > get this change in for the

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

On Sat, Apr 22, 2017 at 10:41:37AM +0200, Mason wrote: > On 22/04/2017 01:43, Russell King - ARM Linux wrote: > > > Or I drop the offending patch (done) and we get the DMA subsystem fixed > > first. Given how long it's been this way, I doubt there's any hurry to > > get this change in for the

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

On 22/04/2017 01:43, Russell King - ARM Linux wrote: > Or I drop the offending patch (done) and we get the DMA subsystem fixed > first. Given how long it's been this way, I doubt there's any hurry to > get this change in for the next merge window. Your solution makes sense. Vinod, could you

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

On 22/04/2017 01:43, Russell King - ARM Linux wrote: > Or I drop the offending patch (done) and we get the DMA subsystem fixed > first. Given how long it's been this way, I doubt there's any hurry to > get this change in for the next merge window. Your solution makes sense. Vinod, could you

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

On Fri, Apr 21, 2017 at 06:12:30PM +1000, Stephen Rothwell wrote: > Hi Mason, > > On Fri, 21 Apr 2017 09:58:58 +0200 Mason wrote: > > > > Anyway, the fix is trivial. > > > > The "pchans_used" field is an unsigned long array. > > for_each_clear_bit_from() expects an unsigned

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

On Fri, Apr 21, 2017 at 06:12:30PM +1000, Stephen Rothwell wrote: > Hi Mason, > > On Fri, 21 Apr 2017 09:58:58 +0200 Mason wrote: > > > > Anyway, the fix is trivial. > > > > The "pchans_used" field is an unsigned long array. > > for_each_clear_bit_from() expects an unsigned long pointer, > >

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

On 21/04/2017 09:58, Mason wrote: > Weird that I didn't catch this when I ran make allyesconfig. Doh! make allyesconfig builds for BE systems. CONFIG_CPU_BIG_ENDIAN=y CONFIG_CPU_ENDIAN_BE8=y But the patch I originally tested with only updated the LE bitops. With the complete patch, I didn't

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

On 21/04/2017 09:58, Mason wrote: > Weird that I didn't catch this when I ran make allyesconfig. Doh! make allyesconfig builds for BE systems. CONFIG_CPU_BIG_ENDIAN=y CONFIG_CPU_ENDIAN_BE8=y But the patch I originally tested with only updated the LE bitops. With the complete patch, I didn't

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

On 21/04/2017 10:12, Stephen Rothwell wrote: > Mason wrote: > >> Anyway, the fix is trivial. >> >> The "pchans_used" field is an unsigned long array. >> for_each_clear_bit_from() expects an unsigned long pointer, >> not an array address. >> >> I'll send a patch to the drivers/dma maintainers. >

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

On 21/04/2017 10:12, Stephen Rothwell wrote: > Mason wrote: > >> Anyway, the fix is trivial. >> >> The "pchans_used" field is an unsigned long array. >> for_each_clear_bit_from() expects an unsigned long pointer, >> not an array address. >> >> I'll send a patch to the drivers/dma maintainers. >

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

Hi Mason, On Fri, 21 Apr 2017 09:58:58 +0200 Mason wrote: > > Anyway, the fix is trivial. > > The "pchans_used" field is an unsigned long array. > for_each_clear_bit_from() expects an unsigned long pointer, > not an array address. > > I'll send a patch to the drivers/dma

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

Hi Mason, On Fri, 21 Apr 2017 09:58:58 +0200 Mason wrote: > > Anyway, the fix is trivial. > > The "pchans_used" field is an unsigned long array. > for_each_clear_bit_from() expects an unsigned long pointer, > not an array address. > > I'll send a patch to the drivers/dma maintainers. The fix

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

On 21/04/2017 00:40, Stephen Rothwell wrote: > After merging the arm tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > In file included from include/linux/bitops.h:36:0, > from include/linux/bitmap.h:7, > from

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

On 21/04/2017 00:40, Stephen Rothwell wrote: > After merging the arm tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > In file included from include/linux/bitops.h:36:0, > from include/linux/bitmap.h:7, > from

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

Hi Russell, After merging the arm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: In file included from include/linux/bitops.h:36:0, from include/linux/bitmap.h:7, from drivers/dma/sun4i-dma.c:11: drivers/dma/sun4i-dma.c: In function

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

Hi Russell, After merging the arm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: In file included from include/linux/bitops.h:36:0, from include/linux/bitmap.h:7, from drivers/dma/sun4i-dma.c:11: drivers/dma/sun4i-dma.c: In function

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

Hi Russell, After merging the arm tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/built-in.o: In function `__sp804_clocksource_and_sched_clock_init': (.init.text+0x1a0e7): undefined reference to `sched_clock_register' Presumably caused by commit 5261ef2ea836

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

Hi Russell, After merging the arm tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/built-in.o: In function `__sp804_clocksource_and_sched_clock_init': (.init.text+0x1a0e7): undefined reference to `sched_clock_register' Presumably caused by commit 5261ef2ea836 (ARM:

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

Hi Russell, After merging the arm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/kernel/iwmmxt.S: Assembler messages: arch/arm/kernel/iwmmxt.S:68: Error: bad instruction `inc_preempt_count r10,r3' arch/arm/kernel/iwmmxt.S:176: Error: bad instruction

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

Hi Russell, After merging the arm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/kernel/iwmmxt.S: Assembler messages: arch/arm/kernel/iwmmxt.S:68: Error: bad instruction `inc_preempt_count r10,r3' arch/arm/kernel/iwmmxt.S:176: Error: bad instruction