From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Build regressions/improvements in v4.0-rc1
Date: Mon, 23 Feb 2015 10:03:10 +0100 [thread overview]
Message-ID: <5900255.NhXvduRnha@wuerfel> (raw)
In-Reply-To: <CAMuHMdXnVLtiSxqwz7ah5faPUx_8piN5eOdNKQtKNwOgT73FqA@mail.gmail.com>
On Monday 23 February 2015 09:45:43 Geert Uytterhoeven wrote:
> On Mon, Feb 23, 2015 at 9:33 AM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > Below is the list of build error/warning regressions/improvements in
> > v4.0-rc1[1] compared to v3.19[2].
> >
> > Summarized:
> > - build errors: +11/-10
>
> > [1] http://kisskb.ellerman.id.au/kisskb/head/8494/ (256 out of 257 configs)
> > [2] http://kisskb.ellerman.id.au/kisskb/head/8427/ (255 out of 257 configs)
> >
> >
> > *** ERRORS ***
> >
> > 11 regressions:
> > + /home/kisskb/slave/src/arch/arm/include/asm/atomic.h: error: #error SMP not supported on pre-ARMv6 CPUs: => 137:2
> > + /home/kisskb/slave/src/arch/arm/include/asm/cmpxchg.h: error: #error "SMP is not supported on this platform": => 114:2
>
> arm-randconfig
>
> SMP does depend on CPU_V6K || CPU_V7 and on HAVE_SMP... strange...
V6/V7 and the earlier V4/V5 are normally mutually exclusive, but we sometimes
screw up the dependencies for some platform, in which case you can end up
with a config that includes both and gives the above error. I'll have a look.
I thought I'd fixed all the bugs we introduced in the merge window in yesterday's
fixes branch.
There is one known problem for mach-realview in this area, for which
I have a fix.
> > + /home/kisskb/slave/src/fs/dax.c: error: implicit declaration of function 'copy_user_page' [-Werror=implicit-function-declaration]: => 266:2
DAX support was merged with 'depends on !(ARM || MIPS || SPARC)', so I don't
see how this could happen.
> sh-randconfig
>
> > + /home/kisskb/slave/src/sound/soc/codecs/max98357a.c: error: implicit declaration of function 'devm_gpiod_get' [-Werror=implicit-function-declaration]: => 55:2
> > + /home/kisskb/slave/src/sound/soc/codecs/max98357a.c: error: implicit declaration of function 'gpiod_direction_output' [-Werror=implicit-function-declaration]: => 61:2
> > + /home/kisskb/slave/src/sound/soc/codecs/max98357a.c: error: implicit declaration of function 'gpiod_set_value' [-Werror=implicit-function-declaration]: => 30:3
Something wrong in arch/sh/include/asm/gpio.h? the codec is only
selectable when gpiolib is enabled, but the consumer.h header
apparently does not get included here.
> s390-allyesconfig
> s390-allmodconfig
> parisc-allmodconfig
> sh-allmodconfig
> sh-allyesconfig
> cris-allyesconfig
> cris-allmodconfig
> mips-allmodconfig
>
> > + error: asm9260_timer.c: undefined reference to `of_io_request_and_map': => .init.text+0x4014), .init.text+0x5c84)
asm9260 is arm-specific, we probably need to refine the dependencies here
to ensure that OF_ADDRESS is set. Need to think about what the best set of
dependencies is.
Arnd
next prev parent reply other threads:[~2015-02-23 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1424680402-3477-1-git-send-email-geert@linux-m68k.org>
2015-02-23 8:45 ` Build regressions/improvements in v4.0-rc1 Geert Uytterhoeven
2015-02-23 9:03 ` Arnd Bergmann [this message]
2015-02-23 9:14 ` Geert Uytterhoeven
2015-02-23 10:24 ` Arnd Bergmann
2015-02-23 10:28 ` Geert Uytterhoeven
2015-02-23 11:24 ` Arnd Bergmann
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=5900255.NhXvduRnha@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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