public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Build regressions/improvements in v3.11-rc1
Date: Tue, 16 Jul 2013 11:47:21 +0200	[thread overview]
Message-ID: <51E516A9.9090705@monstr.eu> (raw)
In-Reply-To: <CAMuHMdWyr_GzDzGBoYn3T85Dqe65FCKd0Y_xvEwwS6UY7naPXQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]

On 07/16/2013 11:29 AM, Geert Uytterhoeven wrote:
> On Tue, Jul 16, 2013 at 11:06 AM, Michal Simek <monstr@monstr.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



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      reply	other threads:[~2013-07-16  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16  7:50 Build regressions/improvements in v3.11-rc1 Geert Uytterhoeven
2013-07-16  7:52 ` Geert Uytterhoeven
2013-07-16  9:06 ` Michal Simek
2013-07-16  9:29   ` Geert Uytterhoeven
2013-07-16  9:47     ` Michal Simek [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=51E516A9.9090705@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@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