public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Levin, Alexander" <alexander.levin@verizon.com>
Cc: 陈华才 <chenhc@lemote.com>, stable <stable@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: mips builds failing in v3.18.38 and v4.1.29
Date: Mon, 1 Aug 2016 14:23:12 -0700	[thread overview]
Message-ID: <20160801212312.GA18005@roeck-us.net> (raw)
In-Reply-To: <84814064-9b38-5be5-37c9-987668d10a00@verizon.com>

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

      reply	other threads:[~2016-08-01 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-31 23:57 mips builds failing in v3.18.38 and v4.1.29 Guenter Roeck
2016-08-01  1:56 ` 陈华才
2016-08-01 14:58   ` Levin, Alexander
2016-08-01 15:29     ` mips " Guenter Roeck
2016-08-01 15:37       ` Levin, Alexander
2016-08-01 21:23         ` Guenter Roeck [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160801212312.GA18005@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=alexander.levin@verizon.com \
    --cc=chenhc@lemote.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox