Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1452917 > unrolled thread

mips builds failing in v3.18.38 and v4.1.29

Back to article view | Back to linux.kernel

Contents

  mips builds failing in v3.18.38 and v4.1.29 Guenter Roeck <linux@roeck-us.net> - 2016-08-01 02:00 +0200
    Re:mips builds failing in v3.18.38 and v4.1.29 "陈华才" <chenhc@lemote.com> - 2016-08-01 07:10 +0200
      Re:mips builds failing in v3.18.38 and v4.1.29 "Levin, Alexander" <alexander.levin@verizon.com> - 2016-08-01 17:10 +0200
        Re: mips builds failing in v3.18.38 and v4.1.29 "Levin, Alexander" <alexander.levin@verizon.com> - 2016-08-01 17:50 +0200
          Re: mips builds failing in v3.18.38 and v4.1.29 Guenter Roeck <linux@roeck-us.net> - 2016-08-02 00:20 +0200
        Re: mips builds failing in v3.18.38 and v4.1.29 Guenter Roeck <linux@roeck-us.net> - 2016-08-01 19:30 +0200

#1452917 — mips builds failing in v3.18.38 and v4.1.29

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 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 fail.

Guenter

[toc] | [next] | [standalone]

#1452988

Hi,

I have already told Sasha that "MIPS: Reserve nosave data for hibernation" should not be backported to 4.1/3.18. But he has no response.

Huacai
 
------------------ Original ------------------
From:  "Guenter Roeck"<linux@roeck-us.net>;
Date:  Mon, Aug 1, 2016 07:57 AM
To:  "Sasha Levin"<sasha.levin@oracle.com>;
Cc:  "stable"<stable@vger.kernel.org>; "linux-kernel@vger.kernel.org"<linux-kernel@vger.kernel.org>; "Huacai Chen"<chenhc@lemote.com>;
Subject:  mips builds failing in v3.18.38 and v4.1.29
 
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 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 fail.

Guenter

[toc] | [prev] | [next] | [standalone]

#1453266

On 07/31/2016 09:56 PM, 陈华才 wrote:
> Hi,
> 
> I have already told Sasha that "MIPS: Reserve nosave data for hibernation" should not be backported to 4.1/3.18. But he has no response.
> 
> Huacai
>  
> ------------------ Original ------------------
> From:  "Guenter Roeck"<linux@roeck-us.net>;
> Date:  Mon, Aug 1, 2016 07:57 AM
> To:  "Sasha Levin"<sasha.levin@oracle.com>;
> Cc:  "stable"<stable@vger.kernel.org>; "linux-kernel@vger.kernel.org"<linux-kernel@vger.kernel.org>; "Huacai Chen"<chenhc@lemote.com>;
> Subject:  mips builds failing in v3.18.38 and v4.1.29
>  
> 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 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 fail.
> 
> Guenter
> 

I'm sorry, it mush have gotten lost in the email switch. I'll revert
that commit for the next stable release and hurry that up.


Thanks,
Sasha

[toc] | [prev] | [next] | [standalone]

#1453286

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 causing all mips builds in 3.18
>>> and 4.1 to fail.
>>>
>>> Guenter
>>>
>>
>> I'm sorry, it mush have gotten lost in the email switch. I'll revert
>> that commit for the next stable release and hurry that up.
>>
> 
> It would be great if you can also address the sparc64 problem
> I reported in my second e-mail.

Yup, I reverted that commit as well.

> Any chance you can add linux@roeck-us.net to your release candidate
> announcement e-mails ? This would help making sure that I don't miss
> a release.

I actually talked with Greg about it a while back and decided to stop
doing "release candidates" because I never ended up getting any reports
on those. I keep getting lots of feedback on the "Added to the x.y
stable kernel" mails so I rely on those for now.

I'll add that mail to the cover letter I send out when I do those, which
is essentially equivalent (and actually gives more time) if that sounds
ok to you.


Thanks,
Sasha

[toc] | [prev] | [next] | [standalone]

#1453495

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 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 fail.
> >>>
> >>> Guenter
> >>>
> >>
> >> I'm sorry, it mush have gotten lost in the email switch. I'll revert
> >> that commit for the next stable release and hurry that up.
> >>
> > 
> > It would be great if you can also address the sparc64 problem
> > I reported in my second e-mail.
> 
> Yup, I reverted that commit as well.
> 
> > Any chance you can add linux@roeck-us.net to your release candidate
> > announcement e-mails ? This would help making sure that I don't miss
> > a release.
> 
> I actually talked with Greg about it a while back and decided to stop
> doing "release candidates" because I never ended up getting any reports
> on those. I keep getting lots of feedback on the "Added to the x.y
> stable kernel" mails so I rely on those for now.
> 
If you didn't get feedback from me, it was because I never got
those e-mails ;-).

> I'll add that mail to the cover letter I send out when I do those, which
> is essentially equivalent (and actually gives more time) if that sounds
> ok to you.
> 
Sure, that would help.

Thanks,
Guenter

[toc] | [prev] | [next] | [standalone]

#1453356

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 fail.
> > 
> > Guenter
> > 
> 
> I'm sorry, it mush have gotten lost in the email switch. I'll revert
> that commit for the next stable release and hurry that up.
> 

It would be great if you can also address the sparc64 problem
I reported in my second e-mail.

Any chance you can add linux@roeck-us.net to your release candidate
announcement e-mails ? This would help making sure that I don't miss
a release.

Thanks,
Guenter

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web