From: Stephen Rothwell s...@canb.auug.org.au
Date: Fri, 29 May 2015 19:18:47 +1000
Nothing in asm/io.h uses anything from vmalloc.h, so remove the include
and fix up the build problems in an allmodconfig (64 bit and 32 bit)
build.
This may be the place where x86 builds get vmalloc.h
Hi Dave,
On Mon, 01 Jun 2015 15:59:31 -0700 (PDT) David Miller da...@davemloft.net
wrote:
From: Stephen Rothwell s...@canb.auug.org.au
Date: Fri, 29 May 2015 19:18:47 +1000
Nothing in asm/io.h uses anything from vmalloc.h, so remove the include
and fix up the build problems in an
Nothing in asm/io.h uses anything from vmalloc.h, so remove the include
and fix up the build problems in an allmodconfig (64 bit and 32 bit)
build.
This may be the place where x86 builds get vmalloc.h implicitly included
and that tends to hide places where vmalloc() et al are added to files
but
* Stephen Rothwell s...@canb.auug.org.au wrote:
Nothing in asm/io.h uses anything from vmalloc.h, so remove the include
and fix up the build problems in an allmodconfig (64 bit and 32 bit)
build.
This may be the place where x86 builds get vmalloc.h implicitly included
and that tends to
Hi Ingo,
On Fri, 29 May 2015 11:21:05 +0200 Ingo Molnar mi...@kernel.org wrote:
Good idea.
Acked-by: Ingo Molnar mi...@kernel.org
Thanks.
Please also test x86 allnoconfig and defconfig 32/64, that tends to unearth
the
remaining places. People doing randconfig testing will find the
At Fri, 29 May 2015 19:18:47 +1000,
Stephen Rothwell wrote:
Nothing in asm/io.h uses anything from vmalloc.h, so remove the include
and fix up the build problems in an allmodconfig (64 bit and 32 bit)
build.
This may be the place where x86 builds get vmalloc.h implicitly included
and that
