Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1628017

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

From Mason <slash.tmp@free.fr>
Newsgroups linux.kernel
Subject Re: linux-next: build failure after merge of the arm tree
Date 2017-04-21 10:00 +0200
Message-ID <tyBDX-39t-11@gated-at.bofh.it> (permalink)
References <tyt3H-6m1-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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 drivers/dma/sun4i-dma.c:11:
> drivers/dma/sun4i-dma.c: In function 'find_and_use_pchan':
> include/linux/bitops.h:56:34: error:
> passing argument 1 of '_find_next_zero_bit_le' from incompatible pointer type [-Werror=incompatible-pointer-types]
>   for ((bit) = find_next_zero_bit((addr), (size), (bit)); \
>                                   ^
> arch/arm/include/asm/bitops.h:200:61: note: in definition of macro 'find_next_zero_bit'
>  #define find_next_zero_bit(p,sz,off) _find_next_zero_bit_le(p,sz,off)
>                                                              ^
> drivers/dma/sun4i-dma.c:241:2: note: in expansion of macro 'for_each_clear_bit_from'
>   for_each_clear_bit_from(i, &priv->pchans_used, max) {
>   ^
> arch/arm/include/asm/bitops.h:163:12: note:
> expected 'const long unsigned int *' but argument is of type 'long unsigned int (*)[1]'
>  extern int _find_next_zero_bit_le(const unsigned long *p, int size, int offset);
>             ^
> [...]
> 
> Caused (or exposed) by commit
> 
>   c4f8ff16b46b ("ARM: 8669/1: bitops: Align prototypes to generic API")
> 
> I have used the arm tree from next-20170420 for today.

Weird that I didn't catch this when I ran make allyesconfig.
https://www.spinics.net/lists/arm-kernel/msg573736.html

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.

$ make C=2 drivers/dma/sun4i-dma.o
  CHECK   drivers/dma/sun4i-dma.c
  CC      drivers/dma/sun4i-dma.o

Regards.

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

linux-next: build failure after merge of the arm tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-04-21 00:50 +0200
  Re: linux-next: build failure after merge of the arm tree Mason <slash.tmp@free.fr> - 2017-04-21 10:00 +0200
    [PATCH] dmaengine: sun4i: fix invalid argument Mason <slash.tmp@free.fr> - 2017-04-21 10:10 +0200
      Re: [PATCH] dmaengine: sun4i: fix invalid argument Maxime Ripard <maxime.ripard@free-electrons.com> - 2017-04-21 10:30 +0200
        [PATCH v2] dmaengine: sun4i: fix invalid argument Mason <slash.tmp@free.fr> - 2017-04-21 10:50 +0200
          Re: [PATCH v2] dmaengine: sun4i: fix invalid argument Maxime Ripard <maxime.ripard@free-electrons.com> - 2017-04-21 17:30 +0200
    Re: linux-next: build failure after merge of the arm tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-04-21 10:20 +0200
      Re: linux-next: build failure after merge of the arm tree Mason <slash.tmp@free.fr> - 2017-04-21 10:40 +0200
      Re: linux-next: build failure after merge of the arm tree Russell King - ARM Linux <linux@armlinux.org.uk> - 2017-04-22 01:50 +0200
        Re: linux-next: build failure after merge of the arm tree Mason <slash.tmp@free.fr> - 2017-04-22 10:50 +0200
          Re: linux-next: build failure after merge of the arm tree Vinod Koul <vinod.koul@intel.com> - 2017-04-24 06:20 +0200
    Re: linux-next: build failure after merge of the arm tree Mason <slash.tmp@free.fr> - 2017-04-21 13:30 +0200

csiph-web