Re: mips builds failing in v3.18.38 and v4.1.29

2016-08-01 Thread Guenter Roeck
On Mon, Aug 01, 2016 at 11:37:31AM -0400, Levin, Alexander wrote: > On 08/01/2016 11:29 AM, Guenter Roeck wrote: > > Hi Sasha, > > > > On Mon, Aug 01, 2016 at 10:58:31AM -0400, Levin, Alexander wrote: > > [ ... ] > >>> > >>> Offending commit is 1dd0964204277108e ("MIPS: Reserve nosave data for >

Re: mips builds failing in v3.18.38 and v4.1.29

2016-08-01 Thread Guenter Roeck
Hi Sasha, On Mon, Aug 01, 2016 at 10:58:31AM -0400, Levin, Alexander wrote: [ ... ] > > > > Offending commit is 1dd0964204277108e ("MIPS: Reserve nosave data for > > hibernation"). > > It fixes a bug which does not exist in 3.18 / 4.1, in turn causing all mips > > builds in 3.18 > > and 4.1 to

Re: mips builds failing in v3.18.38 and v4.1.29

2016-08-01 Thread Levin, Alexander
On 08/01/2016 11:29 AM, Guenter Roeck wrote: > Hi Sasha, > > On Mon, Aug 01, 2016 at 10:58:31AM -0400, Levin, Alexander wrote: > [ ... ] >>> >>> Offending commit is 1dd0964204277108e ("MIPS: Reserve nosave data for >>> hibernation"). >>> It fixes a bug which does not exist in 3.18 / 4.1, in turn

mips builds failing in v3.18.38 and v4.1.29

2016-07-31 Thread Guenter Roeck
Sorry I didn't notice earlier - my 3.18/4.1 build scripts were broken. 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' Offending commit is 1dd0964204277108e ("MIPS: Reserve nosave data for h