From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
Stafford Horne <shorne@gmail.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 19
Date: Thu, 19 Jan 2017 11:42:45 -0500 [thread overview]
Message-ID: <CAP=VYLptRY21K58v6BXj-WoZ1cm9Hv=UPF6z8Owfzct=fobbzQ@mail.gmail.com> (raw)
In-Reply-To: <20170119163959.07a25ca8@canb.auug.org.au>
On Thu, Jan 19, 2017 at 12:39 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Changes since 20170118:
>
> The audit tree gained a conflict against Linus' tree.
>
> The tip tree gained a conflict against the security tree.
>
> The rcu tree gained a semantic conflict against the net-next tree for
> which I applied a merge fix patch.
>
> I dropped 4 patches from the akpm tree that turned up in the tip tree.
>
> Non-merge commits (relative to Linus' tree): 3931
> 4740 files changed, 146960 insertions(+), 87918 deletions(-)
>
The or32 builds started failing in the last couple days:
http://kisskb.ellerman.id.au/kisskb/buildresult/12912013/
I was able to reproduce it locally, and a mindless bisect says:
116ded1356614cff3facc9010125b5a28718cbf1 is the first bad commit
commit 116ded1356614cff3facc9010125b5a28718cbf1
Author: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
Date: Mon May 12 14:08:26 2014 +0300
openrisc: add atomic bitops
I expect the binutils sfr is using is probably similar vintage to
what I've got here locally - from kernel.org crosstool stuff:
$ or32-linux-as --version
GNU assembler (GNU Binutils) 2.20.1.20100303
Copyright 2009 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or later.
This program has absolutely no warranty.
This assembler was configured for a target of `or32-linux'.
Paul.
--
next prev parent reply other threads:[~2017-01-19 16:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 5:39 linux-next: Tree for Jan 19 Stephen Rothwell
2017-01-19 16:42 ` Paul Gortmaker [this message]
2017-01-19 21:59 ` Stafford Horne
2017-01-23 14:11 ` Stafford Horne
2017-01-25 16:37 ` Paul Gortmaker
2017-01-26 4:54 ` Guenter Roeck
2017-01-26 5:38 ` Stafford Horne
2017-01-26 14:22 ` Guenter Roeck
2017-01-26 14:52 ` Paul Gortmaker
2017-01-26 5:45 ` Stafford Horne
2017-01-26 15:08 ` Stafford Horne
2017-01-26 16:19 ` Paul Gortmaker
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 1:51 Stephen Rothwell
2023-01-19 5:45 Stephen Rothwell
2021-01-19 7:03 Stephen Rothwell
2018-01-19 6:55 Stephen Rothwell
2016-01-19 3:11 Stephen Rothwell
2015-01-19 8:23 Stephen Rothwell
2012-01-19 1:59 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=VYLptRY21K58v6BXj-WoZ1cm9Hv=UPF6z8Owfzct=fobbzQ@mail.gmail.com' \
--to=paul.gortmaker@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
/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).