Re: v3.18-stable-queue and v4.1.y-stable-queue build failures

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]