From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Michal Simek <monstr@monstr.eu>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Build regressions/improvements in v3.11-rc1
Date: Tue, 16 Jul 2013 11:29:19 +0200 [thread overview]
Message-ID: <CAMuHMdWyr_GzDzGBoYn3T85Dqe65FCKd0Y_xvEwwS6UY7naPXQ@mail.gmail.com> (raw)
In-Reply-To: <51E50D24.8030900@monstr.eu>
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 ;-)
>> + 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
> 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.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2013-07-16 9:29 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 [this message]
2013-07-16 9:47 ` Michal Simek
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=CAMuHMdWyr_GzDzGBoYn3T85Dqe65FCKd0Y_xvEwwS6UY7naPXQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.