From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from aserp1040.oracle.com ([141.146.126.69]:16682 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161601AbcFGQrH (ORCPT ); Tue, 7 Jun 2016 12:47:07 -0400 Subject: Re: v3.18-stable-queue and v4.1.y-stable-queue build failures To: Guenter Roeck References: <5752DEC5.2040809@roeck-us.net> <57545831.9070106@oracle.com> <5756CD36.8030501@roeck-us.net> Cc: stable , Greg Kroah-Hartman From: Sasha Levin Message-ID: <5756FA58.8030700@oracle.com> Date: Tue, 7 Jun 2016 12:46:16 -0400 MIME-Version: 1.0 In-Reply-To: <5756CD36.8030501@roeck-us.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org List-ID: On 06/07/2016 09:33 AM, Guenter Roeck wrote: > On 06/05/2016 09:49 AM, Sasha Levin wrote: >> On 06/04/2016 09:59 AM, Guenter Roeck wrote: >>> v3.18: >>> >>> arm64:defconfig: >>> >>> drivers/irqchip/irq-gic-v3.c: In function ‘gic_dist_init’: >>> drivers/irqchip/irq-gic-v3.c:319:29: error: ‘GICD_IGROUPR’ >>> >>> drivers/irqchip/irq-gic-v3.c: In function ‘gic_cpu_init’: >>> drivers/irqchip/irq-gic-v3.c:417:29: error: ‘GICR_IGROUPR0’ undeclared >>> >>> All mips builds: >>> >>> arch/mips/kernel/setup.c: In function 'arch_mem_init': >>> arch/mips/kernel/setup.c:689:2: error: implicit declaration of function 'reserve_bootmem_region' >>> >>> >>> v4.1, all mips builds: >>> >>> arch/mips/mm/cache.c: In function '__update_cache': >>> arch/mips/mm/cache.c:134:26: error: implicit declaration of function 'kmap_atomic' >>> arch/mips/mm/cache.c:142:4: error: implicit declaration of function '__kunmap_atomic' >>> >>> arch/mips/kernel/setup.c: In function 'arch_mem_init': >>> arch/mips/kernel/setup.c:690:2: error: implicit declaration of function 'reserve_bootmem_region' >>> >>> Guenter >> >> Thanks Guenter, all should be fixed now. >> > Confirmed. > > Can you let Greg know how you fixed the mips problem in mm/cache.c ? It now affects > 4.4, 4.5, and 4.6 as well. So the commit that was supposed to get this fix was only introduced in 4.2, so I just removed it from the 3.18/4.1 trees, but I suspect Greg will need to do something else here. Thanks, Sasha