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

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

 



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@xxxxxxxxxxxx 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
?韬{.n?????%??檩??w?{.n????{???塄}?财??j:+v??????2??璀??摺?囤??z夸z罐?+?????w棹f




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