From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
"ralf@linux-mips.org" <ralf@linux-mips.org>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 20
Date: Tue, 20 Dec 2016 15:44:30 -0500 [thread overview]
Message-ID: <CAP=VYLpBn=d0U_GXY-BjN=c=CQsCObE2_DqXEws9BHwbMnYGFw@mail.gmail.com> (raw)
In-Reply-To: <20161220125547.72820ddf@canb.auug.org.au>
On Mon, Dec 19, 2016 at 8:55 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Please do not add any material for v4.11 to your linux-next included
> branches until after v4.10-rc1 has been released.
Some recent MIPS build fails showed up, mindless bisect run says:
ad1ccae78b7d7508b39f742631e210407033e8e6 is the first bad commit
commit ad1ccae78b7d7508b39f742631e210407033e8e6
Author: Ralf Baechle <ralf@linux-mips.org>
Date: Thu Dec 15 12:39:22 2016 +0100
MIPS: IP22: Fix build error due to binutils 2.25 uselessnes.
Seems the fix upsets other older junk ; locally I have:
$ mips-linux-ld -v
GNU ld (GNU Binutils) 2.22
Appears on "allnoconfig" and several other mips builds.
I gave Ralf a heads up on IRC as well..
Paul.
--
>
> Changes since 20161219:
>
> The kvm tree lost its build failure.
>
> Non-merge commits (relative to Linus' tree): 566
> 1073 files changed, 26213 insertions(+), 8676 deletions(-)
>
next prev parent reply other threads:[~2016-12-20 20:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 1:55 linux-next: Tree for Dec 20 Stephen Rothwell
2016-12-20 20:44 ` Paul Gortmaker [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-20 9:50 Stephen Rothwell
2022-12-20 0:21 Stephen Rothwell
2021-12-20 11:39 Stephen Rothwell
2019-12-20 5:06 Stephen Rothwell
2019-12-20 11:55 ` Anders Roxell
2019-12-21 18:45 ` Martin K. Petersen
2019-12-23 12:20 ` Anders Roxell
2018-12-20 8:42 Stephen Rothwell
2018-12-20 18:35 ` Guenter Roeck
2017-12-20 4:43 Stephen Rothwell
2013-12-20 6:25 Stephen Rothwell
2012-12-20 6:46 Stephen Rothwell
2011-12-20 8:10 Stephen Rothwell
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='CAP=VYLpBn=d0U_GXY-BjN=c=CQsCObE2_DqXEws9BHwbMnYGFw@mail.gmail.com' \
--to=paul.gortmaker@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).