From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Russell King <rmk@armlinux.org.uk>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mason <slash.tmp@free.fr>
Subject: linux-next: build failure after merge of the arm tree
Date: Fri, 21 Apr 2017 08:40:33 +1000 [thread overview]
Message-ID: <20170421084033.5c987e13@canb.auug.org.au> (raw)
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 '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);
^
include/linux/bitops.h:58:34: error: passing argument 1 of '_find_next_zero_bit_le' from incompatible pointer type [-Werror=incompatible-pointer-types]
(bit) = find_next_zero_bit((addr), (size), (bit) + 1))
^
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.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-04-20 22:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 22:40 Stephen Rothwell [this message]
2017-04-21 7:58 ` linux-next: build failure after merge of the arm tree Mason
2017-04-21 8:06 ` [PATCH] dmaengine: sun4i: fix invalid argument Mason
2017-04-21 8:24 ` Maxime Ripard
2017-04-21 8:43 ` [PATCH v2] " Mason
2017-04-21 14:40 ` Maxime Ripard
2017-04-21 8:12 ` linux-next: build failure after merge of the arm tree Stephen Rothwell
2017-04-21 8:30 ` Mason
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-22 8:41 ` Mason
2017-04-24 4:20 ` Vinod Koul
2017-04-26 22:34 ` [PATCH v2] arm: bitops: Align prototypes to generic API Mason
2017-06-14 19:23 ` linux-next: build failure after merge of the arm tree Mason
2017-04-21 11:27 ` Mason
-- strict thread matches above, loose matches on Subject: below --
2024-05-03 0:15 Stephen Rothwell
2024-05-03 8:18 ` Russell King (Oracle)
2024-05-03 8:23 ` Russell King (Oracle)
2024-05-03 12:08 ` Stephen Rothwell
2024-05-03 12:29 ` Russell King (Oracle)
2022-08-31 9:10 Stephen Rothwell
2022-08-31 9:14 ` Matija Glavinic Pecotic
2021-10-25 23:25 Stephen Rothwell
2020-01-19 21:24 Stephen Rothwell
2020-01-19 21:31 ` Stephen Rothwell
2020-01-19 22:02 ` Russell King - ARM Linux admin
2015-05-29 1:09 Stephen Rothwell
2014-04-10 1:35 Stephen Rothwell
2011-03-02 14:13 Stephen Rothwell
2011-03-02 15:55 ` Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170421084033.5c987e13@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk@armlinux.org.uk \
--cc=slash.tmp@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).