From: Hugo Lefeuvre <hle@owl.eu.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arch@vger.kernel.org
Subject: Re: [asm-generic:master 4/6] arch/powerpc/kernel/iomap.c:142:6: error: conflicting types for 'ioread8_rep'
Date: Mon, 18 Feb 2019 19:18:25 +0100 [thread overview]
Message-ID: <20190218181825.GA18457@behemoth.owl.eu.com.local> (raw)
In-Reply-To: <201902190221.hbMLi4kS%fengguang.wu@intel.com>
Hi Arnd,
On Tue, Feb 19, 2019 at 02:10:34AM +0800, kbuild test robot wrote:
> All errors (new ones prefixed by >>):
>
> >> arch/powerpc/kernel/iomap.c:18:14: error: conflicting types for 'ioread8'
> unsigned int ioread8(void __iomem *addr)
> ^~~~~~~
> In file included from arch/powerpc/include/asm/io.h:653,
> from include/linux/io.h:25,
> from include/linux/irq.h:20,
> from arch/powerpc/include/asm/hardirq.h:6,
> from include/linux/hardirq.h:9,
> from include/linux/interrupt.h:11,
> from include/linux/pci.h:32,
> from arch/powerpc/kernel/iomap.c:7:
> include/asm-generic/iomap.h:29:21: note: previous declaration of 'ioread8' was here
> extern unsigned int ioread8(const void __iomem *addr);
> ^~~~~~~
Just saw that, seems like powerpc headers should be updated as well. Should
I prepare a patch ?
Thanks.
regards,
Hugo
--
Hugo Lefeuvre (hle) | www.owl.eu.com
RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD
ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C
prev parent reply other threads:[~2019-02-18 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 18:10 [asm-generic:master 4/6] arch/powerpc/kernel/iomap.c:142:6: error: conflicting types for 'ioread8_rep' kbuild test robot
2019-02-18 18:18 ` Hugo Lefeuvre [this message]
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=20190218181825.GA18457@behemoth.owl.eu.com.local \
--to=hle@owl.eu.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
/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