[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <51E516A9.9090705@monstr.eu>
Date: Tue, 16 Jul 2013 11:47:21 +0200
From: Michal Simek <monstr@...str.eu>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
CC: Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: Build regressions/improvements in v3.11-rc1
On 07/16/2013 11:29 AM, Geert Uytterhoeven wrote:
> On Tue, Jul 16, 2013 at 11:06 AM, Michal Simek <monstr@...str.eu> wrote:
>> On 07/16/2013 09:50 AM, Geert Uytterhoeven wrote:
>>> + drivers/spi/spi-xilinx.c: error: implicit declaration of function 'ioread32' [-Werror=implicit-function-declaration]: => 105:2
>>> + drivers/spi/spi-xilinx.c: error: implicit declaration of function 'ioread32be' [-Werror=implicit-function-declaration]: => 115:2
>>> + drivers/spi/spi-xilinx.c: error: implicit declaration of function 'iowrite32' [-Werror=implicit-function-declaration]: => 100:2
>>> + drivers/spi/spi-xilinx.c: error: implicit declaration of function 'iowrite32be' [-Werror=implicit-function-declaration]: => 110:2
>
> cris-allyesconfig/cris-allmodconfig, so this can be safely ignored (by you ;-)
Partially because it is my change which is causing these warnings but all architectures
should have these common io functions.
>>> + drivers/video/xilinxfb.c: warning: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'phys_addr_t' [-Wformat]: => 344:3
>
> ppc44x_defconfig
ok. Will fix this.
>> How to find out which target is causing these warnings?
>
> It's indeed a bit difficult without the full logs. /me needs to study kup.
ok.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
Download attachment "signature.asc" of type "application/pgp-signature" (264 bytes)
Powered by blists - more mailing lists