linux-next: build failure after merge of the akpm tree

2020-12-20 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (arm64 allmodconfig) failed like this: ./include/uapi/asm-generic/unistd.h:867:27: error: array index in initializer exceeds array bounds Caused by commit 390e5073c473 ("arch, mm: wire up memfd_secret system call where relevant")

linux-next: build failure after merge of the akpm tree

2020-12-10 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: mm/kasan/quarantine.c: In function 'quarantine_put': mm/kasan/quarantine.c:198:3: error: 'return' with no value, in function returning non-void [-Werror=return-type] 198 | return; |

Re: linux-next: build failure after merge of the akpm tree

2020-12-03 Thread Andrey Konovalov
On Thu, Dec 3, 2020 at 9:52 AM Stephen Rothwell wrote: > > Hi all, > > After merging the akpm tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > mm/kasan/quarantine.c: In function 'quarantine_put': > mm/kasan/quarantine.c:197:15: error: 'info' undeclared (first use in

linux-next: build failure after merge of the akpm tree

2020-12-03 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: mm/kasan/quarantine.c: In function 'quarantine_put': mm/kasan/quarantine.c:197:15: error: 'info' undeclared (first use in this function) 197 | qlink_free(>quarantine_link, cache); |

Re: linux-next: build failure after merge of the akpm tree

2020-11-15 Thread Stephen Rothwell
Hi Mike, On Sun, 15 Nov 2020 11:01:05 +0200 Mike Rapoport wrote: > > My preference would be to put the entire function body in '#ifdef > CONFIG_MEMCG' here. OK, so today I used this: From: Stephen Rothwell Date: Mon, 16 Nov 2020 16:55:10 +1100 Subject: [PATCH]

Re: linux-next: build failure after merge of the akpm tree

2020-11-15 Thread Mike Rapoport
On Fri, Nov 13, 2020 at 05:14:52PM -0800, Andrew Morton wrote: > On Fri, 13 Nov 2020 18:02:39 +1100 Stephen Rothwell > wrote: > > > Hi all, > > > > After merging the akpm tree, today's linux-next build (i386 defconfig) > > failed like this: > > > > mm/secretmem.c: In function

Re: linux-next: build failure after merge of the akpm tree

2020-11-13 Thread Andrew Morton
On Fri, 13 Nov 2020 18:02:39 +1100 Stephen Rothwell wrote: > Hi all, > > After merging the akpm tree, today's linux-next build (i386 defconfig) > failed like this: > > mm/secretmem.c: In function 'secretmem_memcg_charge': > mm/secretmem.c:72:4: error: 'struct page' has no member named

linux-next: build failure after merge of the akpm tree

2020-11-12 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (i386 defconfig) failed like this: mm/secretmem.c: In function 'secretmem_memcg_charge': mm/secretmem.c:72:4: error: 'struct page' has no member named 'memcg_data' 72 | p->memcg_data = page->memcg_data; |^~

linux-next: build failure after merge of the akpm tree

2020-11-10 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: mm/kasan/shadow.c: In function 'kasan_poison_memory': mm/kasan/shadow.c:88:6: error: implicit declaration of function 'is_kfence_address' [-Werror=implicit-function-declaration] 88 | if

Re: linux-next: build failure after merge of the akpm tree

2020-09-28 Thread Christoph Hellwig
Thanks, the fix looks correct.

linux-next: build failure after merge of the akpm tree

2020-09-28 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: mm/madvise.c: In function '__do_sys_process_madvise': mm/madvise.c:1194:9: error: implicit declaration of function 'compat_import_iovec'; did you mean 'import_iovec'?

linux-next: build failure after merge of the akpm tree

2020-09-08 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: mm/madvise.c: In function 'madv_import_iovec': mm/madvise.c:1233:6: error: implicit declaration of function 'in_compat_syscall' [-Werror=implicit-function-declaration] 1233 | if

Re: linux-next: build failure after merge of the akpm tree

2020-06-04 Thread Stephen Rothwell
Hi all, On Thu, 4 Jun 2020 16:44:42 +1000 Stephen Rothwell wrote: > > Hi all, > > After merging the akpm tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > arch/powerpc/mm/ptdump/ptdump.c: In function 'walk_pagetables': > arch/powerpc/mm/ptdump/ptdump.c:337:25:

linux-next: build failure after merge of the akpm tree

2020-06-04 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (powerpc allyesconfig) failed like this: arch/powerpc/mm/ptdump/ptdump.c: In function 'walk_pagetables': arch/powerpc/mm/ptdump/ptdump.c:337:25: error: implicit declaration of function 'pgd_is_leaf'; did you mean 'p4d_is_leaf'?

Re: linux-next: build failure after merge of the akpm tree

2020-06-02 Thread Andrew Morton
On Tue, 2 Jun 2020 19:57:41 +1000 Stephen Rothwell wrote: > Subject: [PATCH] turns out that probe_user_write is used in modular code > > Signed-off-by: Stephen Rothwell > --- > mm/maccess.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/mm/maccess.c b/mm/maccess.c > index

linux-next: build failure after merge of the akpm tree

2020-06-02 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: ERROR: modpost: ".probe_user_write" [arch/powerpc/kvm/kvm-hv.ko] undefined! Caused by patch "maccess: unexport probe_kernel_write and probe_user_write" "These two functions are not used

Re: linux-next: build failure after merge of the akpm tree

2020-05-28 Thread Christoph Hellwig
This looks correct, thanks.

linux-next: build failure after merge of the akpm tree

2020-05-28 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c: In function 'kfd_sdma_activity_worker': drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c:117:2: error: implicit declaration of function

Re: linux-next: build failure after merge of the akpm tree

2020-05-25 Thread Stephen Rothwell
Hi John, On Mon, 25 May 2020 11:18:46 -0700 John Hubbard wrote: > > Yes, looks good. And in fact, Andrew has the same fix-up in the mmotm branch > of > linux-next.git, as > > commit a76c281a8ddd > ("mmap-locking-api-rename-mmap_sem-to-mmap_lock-fix"). For some reason that was not

Re: linux-next: build failure after merge of the akpm tree

2020-05-25 Thread John Hubbard
On 2020-05-25 05:17, Stephen Rothwell wrote: Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/kernel.h:14, from mm/gup.c:2: mm/gup.c: In function 'internal_get_user_pages_fast':

linux-next: build failure after merge of the akpm tree

2020-05-25 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/kernel.h:14, from mm/gup.c:2: mm/gup.c: In function 'internal_get_user_pages_fast': mm/gup.c:2732:33: error: 'struct mm_struct' has no member

Re: linux-next: build failure after merge of the akpm tree

2019-02-26 Thread Mike Rapoport
On Tue, Feb 26, 2019 at 06:39:15PM +1100, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc > allnoconfig) failed like this: > > /home/sfr/next/next/arch/powerpc/kernel/setup_32.c:176:21: error: > redefinition of 'alloc_stack' > static void

linux-next: build failure after merge of the akpm tree

2019-02-25 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc allnoconfig) failed like this: /home/sfr/next/next/arch/powerpc/kernel/setup_32.c:176:21: error: redefinition of 'alloc_stack' static void *__init alloc_stack(void) ^~~

Re: linux-next: build failure after merge of the akpm tree

2018-12-12 Thread Stephen Rothwell
Hi Anshuman, On Wed, 12 Dec 2018 22:35:38 +0530 Anshuman Khandual wrote: > > On 12/03/2018 12:30 PM, Stephen Rothwell wrote: > > Hi Andrew, > > > > After merging the akpm tree, today's linux-next build (powerpc_le perf) > > failed like this: > > > > bench/numa.c:37:10: fatal error:

Re: linux-next: build failure after merge of the akpm tree

2018-12-12 Thread Anshuman Khandual
On 12/03/2018 12:30 PM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc_le perf) > failed like this: > > bench/numa.c:37:10: fatal error: linux/numa.h: No such file or directory > #include > ^~ > > Caused by

Re: linux-next: build failure after merge of the akpm tree

2018-12-03 Thread Anshuman Khandual
On 12/03/2018 12:30 PM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc_le perf) > failed like this: > > bench/numa.c:37:10: fatal error: linux/numa.h: No such file or directory > #include > ^~ > > Caused by

Re: linux-next: build failure after merge of the akpm tree

2018-12-03 Thread Anshuman Khandual
On 12/03/2018 12:30 PM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc_le perf) > failed like this: > > bench/numa.c:37:10: fatal error: linux/numa.h: No such file or directory > #include > ^~ > > Caused by

linux-next: build failure after merge of the akpm tree

2018-12-02 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc_le perf) failed like this: bench/numa.c:37:10: fatal error: linux/numa.h: No such file or directory #include ^~ Caused by patches "mm: replace all open encodings for NUMA_NO_NODE"

linux-next: build failure after merge of the akpm tree

2018-12-02 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc_le perf) failed like this: bench/numa.c:37:10: fatal error: linux/numa.h: No such file or directory #include ^~ Caused by patches "mm: replace all open encodings for NUMA_NO_NODE"

Re: linux-next: build failure after merge of the akpm tree

2018-11-30 Thread Anshuman Khandual
On 11/30/2018 11:00 AM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc_le perf) > failed like this: > > bench/numa.c: In function 'bind_to_node': > bench/numa.c:301:21: error: 'NUMA_NO_NODE' undeclared (first use in this > function);

Re: linux-next: build failure after merge of the akpm tree

2018-11-30 Thread Anshuman Khandual
On 11/30/2018 11:00 AM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc_le perf) > failed like this: > > bench/numa.c: In function 'bind_to_node': > bench/numa.c:301:21: error: 'NUMA_NO_NODE' undeclared (first use in this > function);

linux-next: build failure after merge of the akpm tree

2018-11-29 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc_le perf) failed like this: bench/numa.c: In function 'bind_to_node': bench/numa.c:301:21: error: 'NUMA_NO_NODE' undeclared (first use in this function); did you mean 'NUMA_NUM_NODES'? if (target_node == NUMA_NO_NODE) {

linux-next: build failure after merge of the akpm tree

2018-11-29 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc_le perf) failed like this: bench/numa.c: In function 'bind_to_node': bench/numa.c:301:21: error: 'NUMA_NO_NODE' undeclared (first use in this function); did you mean 'NUMA_NUM_NODES'? if (target_node == NUMA_NO_NODE) {

Re: linux-next: build failure after merge of the akpm tree

2018-10-16 Thread Ingo Molnar
* Stephen Rothwell wrote: > Hi all, > > On Mon, 8 Oct 2018 19:03:41 +1100 Stephen Rothwell > wrote: > > > > After merging the akpm tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > arch/x86/mm/kaslr.c:26:10: fatal error: linux/bootmem.h: No such file or >

Re: linux-next: build failure after merge of the akpm tree

2018-10-16 Thread Ingo Molnar
* Stephen Rothwell wrote: > Hi all, > > On Mon, 8 Oct 2018 19:03:41 +1100 Stephen Rothwell > wrote: > > > > After merging the akpm tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > arch/x86/mm/kaslr.c:26:10: fatal error: linux/bootmem.h: No such file or >

Re: linux-next: build failure after merge of the akpm tree

2018-10-15 Thread Stephen Rothwell
Hi all, On Mon, 8 Oct 2018 19:03:41 +1100 Stephen Rothwell wrote: > > After merging the akpm tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > arch/x86/mm/kaslr.c:26:10: fatal error: linux/bootmem.h: No such file or > directory > #include >

Re: linux-next: build failure after merge of the akpm tree

2018-10-15 Thread Stephen Rothwell
Hi all, On Mon, 8 Oct 2018 19:03:41 +1100 Stephen Rothwell wrote: > > After merging the akpm tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > arch/x86/mm/kaslr.c:26:10: fatal error: linux/bootmem.h: No such file or > directory > #include >

linux-next: build failure after merge of the akpm tree

2018-10-08 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: arch/x86/mm/kaslr.c:26:10: fatal error: linux/bootmem.h: No such file or directory #include ^ Caused by patch "mm: remove include/linux/bootmem.h" interacting

linux-next: build failure after merge of the akpm tree

2018-10-08 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: arch/x86/mm/kaslr.c:26:10: fatal error: linux/bootmem.h: No such file or directory #include ^ Caused by patch "mm: remove include/linux/bootmem.h" interacting

linux-next: build failure after merge of the akpm tree

2018-10-02 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allnoconfig) failed like this: Caused by commit a20bb0583751 ("dma-direct: add an explicit dma_direct_get_required_mask") from the dma-mappgin tree conflicting with patch "mm: remove include/linux/bootmem.h" I have

linux-next: build failure after merge of the akpm tree

2018-10-02 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allnoconfig) failed like this: Caused by commit a20bb0583751 ("dma-direct: add an explicit dma_direct_get_required_mask") from the dma-mappgin tree conflicting with patch "mm: remove include/linux/bootmem.h" I have

Re: linux-next: build failure after merge of the akpm tree

2018-03-21 Thread Stephen Rothwell
Hi Greg, On Wed, 21 Mar 2018 11:02:08 +0100 Greg Kroah-Hartman wrote: > > Patch is now queued up, thanks. Excellent. -- Cheers, Stephen Rothwell pgpMuNJUwYuTO.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the akpm tree

2018-03-21 Thread Stephen Rothwell
Hi Greg, On Wed, 21 Mar 2018 11:02:08 +0100 Greg Kroah-Hartman wrote: > > Patch is now queued up, thanks. Excellent. -- Cheers, Stephen Rothwell pgpMuNJUwYuTO.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the akpm tree

2018-03-21 Thread Greg Kroah-Hartman
On Wed, Mar 21, 2018 at 07:17:27PM +1100, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > drivers/base/firmware_loader/fallback.c: In function 'map_fw_priv_pages': >

Re: linux-next: build failure after merge of the akpm tree

2018-03-21 Thread Greg Kroah-Hartman
On Wed, Mar 21, 2018 at 07:17:27PM +1100, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > drivers/base/firmware_loader/fallback.c: In function 'map_fw_priv_pages': >

linux-next: build failure after merge of the akpm tree

2018-03-21 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/base/firmware_loader/fallback.c: In function 'map_fw_priv_pages': drivers/base/firmware_loader/fallback.c:232:2: error: implicit declaration of function 'vunmap'; did you mean

linux-next: build failure after merge of the akpm tree

2018-03-21 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/base/firmware_loader/fallback.c: In function 'map_fw_priv_pages': drivers/base/firmware_loader/fallback.c:232:2: error: implicit declaration of function 'vunmap'; did you mean

linux-next: build failure after merge of the akpm tree

2017-11-05 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: lib/cpumask.c: In function 'cpumask_next_and': lib/cpumask.c:39:9: error: implicit declaration of function 'find_next_and_bit' [-Werror=implicit-function-declaration] return

linux-next: build failure after merge of the akpm tree

2017-11-05 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: lib/cpumask.c: In function 'cpumask_next_and': lib/cpumask.c:39:9: error: implicit declaration of function 'find_next_and_bit' [-Werror=implicit-function-declaration] return

Re: linux-next: build failure after merge of the akpm tree

2017-08-01 Thread Arnd Bergmann
On Tue, Aug 1, 2017 at 8:40 PM, Kees Cook wrote: >> >> I don't know why this has turned up now. I have just left it broken >> for now and would appreciate any fix. > > Thanks for the heads-up! I'm not sure why this suddenly appeared > either, but Arnd has sent a patch for

Re: linux-next: build failure after merge of the akpm tree

2017-08-01 Thread Arnd Bergmann
On Tue, Aug 1, 2017 at 8:40 PM, Kees Cook wrote: >> >> I don't know why this has turned up now. I have just left it broken >> for now and would appreciate any fix. > > Thanks for the heads-up! I'm not sure why this suddenly appeared > either, but Arnd has sent a patch for this now. The main

Re: linux-next: build failure after merge of the akpm tree

2017-08-01 Thread Kees Cook
On Mon, Jul 31, 2017 at 11:25 PM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > In file included from arch/powerpc/include/asm/paca.h:19:0, > from

Re: linux-next: build failure after merge of the akpm tree

2017-08-01 Thread Kees Cook
On Mon, Jul 31, 2017 at 11:25 PM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > In file included from arch/powerpc/include/asm/paca.h:19:0, > from

linux-next: build failure after merge of the akpm tree

2017-08-01 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from arch/powerpc/include/asm/paca.h:19:0, from arch/powerpc/include/asm/hw_irq.h:42, from arch/powerpc/include/asm/irqflags.h:11,

linux-next: build failure after merge of the akpm tree

2017-08-01 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from arch/powerpc/include/asm/paca.h:19:0, from arch/powerpc/include/asm/hw_irq.h:42, from arch/powerpc/include/asm/irqflags.h:11,

Re: linux-next: build failure after merge of the akpm tree

2017-07-03 Thread David Miller
From: Stephen Rothwell Date: Fri, 30 Jun 2017 16:32:41 +1000 > From: Stephen Rothwell > Date: Fri, 30 Jun 2017 16:24:35 +1000 > Subject: [PATCH] net/mlx5: fix memcpy limit? > > Signed-off-by: Stephen Rothwell Applied,

Re: linux-next: build failure after merge of the akpm tree

2017-07-03 Thread David Miller
From: Stephen Rothwell Date: Fri, 30 Jun 2017 16:32:41 +1000 > From: Stephen Rothwell > Date: Fri, 30 Jun 2017 16:24:35 +1000 > Subject: [PATCH] net/mlx5: fix memcpy limit? > > Signed-off-by: Stephen Rothwell Applied, thanks.

Re: linux-next: build failure after merge of the akpm tree

2017-07-03 Thread Stephen Rothwell
Hi all, On Fri, 30 Jun 2017 16:32:41 +1000 Stephen Rothwell wrote: > > After merging the akpm tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from include/linux/bitmap.h:8:0, > from

Re: linux-next: build failure after merge of the akpm tree

2017-07-03 Thread Stephen Rothwell
Hi all, On Fri, 30 Jun 2017 16:32:41 +1000 Stephen Rothwell wrote: > > After merging the akpm tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from include/linux/bitmap.h:8:0, > from include/linux/cpumask.h:11, >

linux-next: build failure after merge of the akpm tree

2017-06-30 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/bitmap.h:8:0, from include/linux/cpumask.h:11, from include/linux/mm_types_task.h:13, from

linux-next: build failure after merge of the akpm tree

2017-06-30 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/bitmap.h:8:0, from include/linux/cpumask.h:11, from include/linux/mm_types_task.h:13, from

Re: linux-next: build failure after merge of the akpm tree

2017-06-26 Thread Stephen Rothwell
Hi Michal, On Mon, 26 Jun 2017 09:13:46 +0200 Michal Hocko wrote: > > On Mon 26-06-17 16:53:43, Stephen Rothwell wrote: > > > > After merging the akpm tree, today's linux-next build (sparc64 defconfig) > > failed like this: > > > > arch/sparc/kernel/mdesc.c: In function

Re: linux-next: build failure after merge of the akpm tree

2017-06-26 Thread Stephen Rothwell
Hi Michal, On Mon, 26 Jun 2017 09:13:46 +0200 Michal Hocko wrote: > > On Mon 26-06-17 16:53:43, Stephen Rothwell wrote: > > > > After merging the akpm tree, today's linux-next build (sparc64 defconfig) > > failed like this: > > > > arch/sparc/kernel/mdesc.c: In function 'mdesc_kmalloc': > >

Re: linux-next: build failure after merge of the akpm tree

2017-06-26 Thread Michal Hocko
On Mon 26-06-17 16:53:43, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (sparc64 defconfig) > failed like this: > > arch/sparc/kernel/mdesc.c: In function 'mdesc_kmalloc': > arch/sparc/kernel/mdesc.c:208:48: error: '__GFP_REPEAT' undeclared (first

Re: linux-next: build failure after merge of the akpm tree

2017-06-26 Thread Michal Hocko
On Mon 26-06-17 16:53:43, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (sparc64 defconfig) > failed like this: > > arch/sparc/kernel/mdesc.c: In function 'mdesc_kmalloc': > arch/sparc/kernel/mdesc.c:208:48: error: '__GFP_REPEAT' undeclared (first

linux-next: build failure after merge of the akpm tree

2017-06-26 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (sparc64 defconfig) failed like this: arch/sparc/kernel/mdesc.c: In function 'mdesc_kmalloc': arch/sparc/kernel/mdesc.c:208:48: error: '__GFP_REPEAT' undeclared (first use in this function) base = kmalloc(handle_size + 15,

linux-next: build failure after merge of the akpm tree

2017-06-26 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (sparc64 defconfig) failed like this: arch/sparc/kernel/mdesc.c: In function 'mdesc_kmalloc': arch/sparc/kernel/mdesc.c:208:48: error: '__GFP_REPEAT' undeclared (first use in this function) base = kmalloc(handle_size + 15,

linux-next: build failure after merge of the akpm tree

2017-04-20 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: fs/gfs2/bmap.c: In function 'sweep_bh_for_rgrps': fs/gfs2/bmap.c:1075:5: error: 'CURRENT_TIME' undeclared (first use in this function) CURRENT_TIME; ^ fs/gfs2/bmap.c:1075:5: note:

linux-next: build failure after merge of the akpm tree

2017-04-20 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: fs/gfs2/bmap.c: In function 'sweep_bh_for_rgrps': fs/gfs2/bmap.c:1075:5: error: 'CURRENT_TIME' undeclared (first use in this function) CURRENT_TIME; ^ fs/gfs2/bmap.c:1075:5: note:

linux-next: build failure after merge of the akpm tree

2017-04-18 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: arch/x86/kernel/kprobes/opt.c: In function 'arch_prepare_optimized_kprobe': arch/x86/kernel/kprobes/opt.c:357:2: error: implicit declaration of function 'set_memory_rw'

linux-next: build failure after merge of the akpm tree

2017-04-18 Thread Stephen Rothwell
Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: arch/x86/kernel/kprobes/opt.c: In function 'arch_prepare_optimized_kprobe': arch/x86/kernel/kprobes/opt.c:357:2: error: implicit declaration of function 'set_memory_rw'

linux-next: build failure after merge of the akpm tree

2017-04-10 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: mm/migrate.c: In function 'migrate_vma_insert_page': mm/migrate.c:2491:23: error: passing argument 2 of 'pud_alloc' from incompatible pointer type [-Werror=incompatible-pointer-types] pudp

linux-next: build failure after merge of the akpm tree

2017-04-10 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: mm/migrate.c: In function 'migrate_vma_insert_page': mm/migrate.c:2491:23: error: passing argument 2 of 'pud_alloc' from incompatible pointer type [-Werror=incompatible-pointer-types] pudp

Re: linux-next: build failure after merge of the akpm tree

2017-03-20 Thread Michal Hocko
On Mon 20-03-17 16:37:35, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > fs/f2fs/node.c: In function 'init_free_nid_cache': > fs/f2fs/node.c:2634:25: error: implicit declaration of function >

Re: linux-next: build failure after merge of the akpm tree

2017-03-20 Thread Michal Hocko
On Mon 20-03-17 16:37:35, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > fs/f2fs/node.c: In function 'init_free_nid_cache': > fs/f2fs/node.c:2634:25: error: implicit declaration of function >

Re: linux-next: build failure after merge of the akpm tree

2017-03-20 Thread Jaegeuk Kim
On 03/20, Michal Hocko wrote: > On Mon 20-03-17 16:37:35, Stephen Rothwell wrote: > > Hi Andrew, > > > > After merging the akpm tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > fs/f2fs/node.c: In function 'init_free_nid_cache': > > fs/f2fs/node.c:2634:25: error:

Re: linux-next: build failure after merge of the akpm tree

2017-03-20 Thread Jaegeuk Kim
On 03/20, Michal Hocko wrote: > On Mon 20-03-17 16:37:35, Stephen Rothwell wrote: > > Hi Andrew, > > > > After merging the akpm tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > fs/f2fs/node.c: In function 'init_free_nid_cache': > > fs/f2fs/node.c:2634:25: error:

linux-next: build failure after merge of the akpm tree

2017-03-19 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: fs/f2fs/node.c: In function 'init_free_nid_cache': fs/f2fs/node.c:2634:25: error: implicit declaration of function 'f2fs_kvzalloc' [-Werror=implicit-function-declaration]

linux-next: build failure after merge of the akpm tree

2017-03-19 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: fs/f2fs/node.c: In function 'init_free_nid_cache': fs/f2fs/node.c:2634:25: error: implicit declaration of function 'f2fs_kvzalloc' [-Werror=implicit-function-declaration]

Re: linux-next: build failure after merge of the akpm tree

2017-03-06 Thread Laura Abbott
On 03/06/2017 07:07 PM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/net/sock.h:64:0, > from include/linux/tcp.h:23, > from

Re: linux-next: build failure after merge of the akpm tree

2017-03-06 Thread Laura Abbott
On 03/06/2017 07:07 PM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/net/sock.h:64:0, > from include/linux/tcp.h:23, > from

linux-next: build failure after merge of the akpm tree

2017-03-06 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/net/sock.h:64:0, from include/linux/tcp.h:23, from include/linux/ipv6.h:83, from include/net/ipv6.h:16,

linux-next: build failure after merge of the akpm tree

2017-03-06 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/net/sock.h:64:0, from include/linux/tcp.h:23, from include/linux/ipv6.h:83, from include/net/ipv6.h:16,

linux-next: build failure after merge of the akpm tree

2017-03-06 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/kernel/machine_kexec.c: In function 'machine_kexec': arch/arm/kernel/machine_kexec.c:163:2: error: implicit declaration of function 'set_kernel_text_rw'

linux-next: build failure after merge of the akpm tree

2017-03-06 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/kernel/machine_kexec.c: In function 'machine_kexec': arch/arm/kernel/machine_kexec.c:163:2: error: implicit declaration of function 'set_kernel_text_rw'

linux-next: build failure after merge of the akpm tree

2017-01-08 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: lib/radix-tree.c: In function 'radix_tree_iter_delete': lib/radix-tree.c:1952:3: error: too few arguments to function '__radix_tree_delete_node' __radix_tree_delete_node(root, node);

linux-next: build failure after merge of the akpm tree

2017-01-08 Thread Stephen Rothwell
Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) failed like this: lib/radix-tree.c: In function 'radix_tree_iter_delete': lib/radix-tree.c:1952:3: error: too few arguments to function '__radix_tree_delete_node' __radix_tree_delete_node(root, node);

Re: linux-next: build failure after merge of the akpm tree

2016-01-26 Thread Takashi Iwai
On Tue, 26 Jan 2016 21:51:30 +0100, Stephen Rothwell wrote: > > Hi Takashi, > > On Mon, 25 Jan 2016 14:45:55 +0100 Takashi Iwai wrote: > > > > From: Takashi Iwai > > Subject: [PATCH v2] ALSA: compress: Disable GET_CODEC_CAPS ioctl for some > > architectures > > > > Some architectures like

Re: linux-next: build failure after merge of the akpm tree

2016-01-26 Thread Stephen Rothwell
Hi Takashi, On Mon, 25 Jan 2016 14:45:55 +0100 Takashi Iwai wrote: > > From: Takashi Iwai > Subject: [PATCH v2] ALSA: compress: Disable GET_CODEC_CAPS ioctl for some > architectures > > Some architectures like PowerPC can handle the maximum struct size in > an ioctl only up to 13 bits, and

Re: linux-next: build failure after merge of the akpm tree

2016-01-26 Thread Vinod Koul
On Mon, Jan 25, 2016 at 01:55:46PM +, Mark Brown wrote: > > though we will need to come up with an alternative solution for the > affected architectures if anyone ends up caring (MIPS or PowerPC might > possibly). Okay I did some rethink on this. So we should be able to make

Re: linux-next: build failure after merge of the akpm tree

2016-01-26 Thread Vinod Koul
On Mon, Jan 25, 2016 at 02:45:55PM +0100, Takashi Iwai wrote: > Below is the revised one. Acked-by: Vinod Koul Thanks for fixing this up... -- ~Vinod

Re: linux-next: build failure after merge of the akpm tree

2016-01-26 Thread Vinod Koul
On Mon, Jan 25, 2016 at 02:45:55PM +0100, Takashi Iwai wrote: > Below is the revised one. Acked-by: Vinod Koul Thanks for fixing this up... -- ~Vinod

Re: linux-next: build failure after merge of the akpm tree

2016-01-26 Thread Stephen Rothwell
Hi Takashi, On Mon, 25 Jan 2016 14:45:55 +0100 Takashi Iwai wrote: > > From: Takashi Iwai > Subject: [PATCH v2] ALSA: compress: Disable GET_CODEC_CAPS ioctl for some > architectures > > Some architectures like PowerPC can handle the maximum struct size in > an

Re: linux-next: build failure after merge of the akpm tree

2016-01-26 Thread Takashi Iwai
On Tue, 26 Jan 2016 21:51:30 +0100, Stephen Rothwell wrote: > > Hi Takashi, > > On Mon, 25 Jan 2016 14:45:55 +0100 Takashi Iwai wrote: > > > > From: Takashi Iwai > > Subject: [PATCH v2] ALSA: compress: Disable GET_CODEC_CAPS ioctl for some > > architectures > >

Re: linux-next: build failure after merge of the akpm tree

2016-01-26 Thread Vinod Koul
On Mon, Jan 25, 2016 at 01:55:46PM +, Mark Brown wrote: > > though we will need to come up with an alternative solution for the > affected architectures if anyone ends up caring (MIPS or PowerPC might > possibly). Okay I did some rethink on this. So we should be able to make

Re: linux-next: build failure after merge of the akpm tree

2016-01-25 Thread Sudip Mukherjee
On Mon, Jan 25, 2016 at 02:45:55PM +0100, Takashi Iwai wrote: > On Mon, 25 Jan 2016 14:10:37 +0100, > Takashi Iwai wrote: > > > > On Mon, 25 Jan 2016 12:41:50 +0100, > > Mark Brown wrote: > > > > > > > Signed-off-by: Takashi Iwai > > --- > > sound/core/compress_offload.c | 11 +++ > >

Re: linux-next: build failure after merge of the akpm tree

2016-01-25 Thread Mark Brown
On Mon, Jan 25, 2016 at 02:45:55PM +0100, Takashi Iwai wrote: > Argh, a typo here. I forgot to refresh the patch, sorry. > Below is the revised one. This makes sense to me. Reviwed-by: Mark Brown though we will need to come up with an alternative solution for the affected architectures if

Re: linux-next: build failure after merge of the akpm tree

2016-01-25 Thread Takashi Iwai
On Mon, 25 Jan 2016 14:10:37 +0100, Takashi Iwai wrote: > > On Mon, 25 Jan 2016 12:41:50 +0100, > Mark Brown wrote: > > > > On Mon, Jan 25, 2016 at 10:29:54AM +0100, Takashi Iwai wrote: > > > Stephen Rothwell wrote: > > > > > > diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig >

Re: linux-next: build failure after merge of the akpm tree

2016-01-25 Thread Takashi Iwai
On Mon, 25 Jan 2016 12:41:50 +0100, Mark Brown wrote: > > On Mon, Jan 25, 2016 at 10:29:54AM +0100, Takashi Iwai wrote: > > Stephen Rothwell wrote: > > > > diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig > > > index 50693c867e71..ee5f36b9c787 100644 > > > ---

Re: linux-next: build failure after merge of the akpm tree

2016-01-25 Thread Mark Brown
On Mon, Jan 25, 2016 at 10:29:54AM +0100, Takashi Iwai wrote: > Stephen Rothwell wrote: > > diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig > > index 50693c867e71..ee5f36b9c787 100644 > > --- a/sound/soc/codecs/Kconfig > > +++ b/sound/soc/codecs/Kconfig > > @@ -13,6 +13,7 @@ menu

  1   2   3   4   >