From: Chris Metcalf <cmetcalf@mellanox•com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org,
"Peter Zijlstra (Intel)" <peterz@infradead•org>,
Ingo Molnar <mingo@kernel•org>
Cc: linux-kernel@vger•kernel.org, linux-arch@vger•kernel.org
Subject: Re: linux-next: Tree for Jun 21
Date: Tue, 21 Jun 2016 08:08:29 -0400 [thread overview]
Message-ID: <f43656af-050c-82b3-e10d-66be072be320@mellanox.com> (raw)
In-Reply-To: <5768E650.2080506@gmail.com>
On 6/21/2016 3:01 AM, Sudip Mukherjee wrote:
> On Tuesday 21 June 2016 06:46 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20160620:
>
> tilepro defconfig is failing while doing "make prepare" and bisect shows the first bad commit as:
>
> 1af5de9af138 ("locking/atomic, arch/tile: Implement atomic{,64}_fetch_{add,sub,and,or,xor}()")
>
> You can find today's build log at:
> https://travis-ci.org/sudipm-mukherjee/parport/jobs/139112570
On inspection, I note that the arch/tile/include/atomic_32.h header has
ATOMIC64_OP(and)
ATOMIC64_OP(or)
ATOMIC64_OP(xor)
but these should be ATOMIC64_OPS, plural.
Peter, what toolchain were you using for tilepro build testing? You need to have a tilepro toolchain (not tilegx) and build with ARCH=tilepro.
--
Chris Metcalf, Mellanox Technologies
http://www.mellanox.com
next prev parent reply other threads:[~2016-06-21 12:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 5:46 linux-next: Tree for Jun 21 Stephen Rothwell
2016-06-21 7:01 ` Sudip Mukherjee
2016-06-21 7:58 ` Peter Zijlstra
2016-06-21 8:55 ` Sudip Mukherjee
2016-06-21 12:08 ` Chris Metcalf [this message]
2016-06-21 12:42 ` Peter Zijlstra
2016-06-21 13:47 ` Chris Metcalf
2016-06-21 14:04 ` Peter Zijlstra
2016-06-21 14:14 ` Peter Zijlstra
2016-06-21 14:20 ` Chris Metcalf
2016-06-21 14:25 ` Peter Zijlstra
2016-06-21 14:34 ` Sudip Mukherjee
2016-06-21 15:26 ` Chris Metcalf
2016-06-21 17:06 ` Peter Zijlstra
2016-06-21 17:29 ` Peter Zijlstra
2016-06-21 18:28 ` Peter Zijlstra
2016-06-21 18:36 ` Chris Metcalf
2016-06-21 18:50 ` Peter Zijlstra
2016-06-21 19:04 ` Peter Zijlstra
2016-06-21 21:14 ` Arnd Bergmann
2016-06-22 20:43 ` Chris Metcalf
2016-06-22 21:05 ` Peter Zijlstra
2016-06-22 9:16 ` Peter Zijlstra
2016-06-22 20:40 ` Chris Metcalf
-- strict thread matches above, loose matches on Subject: below --
2024-06-21 18:36 Mark Brown
2023-06-21 4:59 Stephen Rothwell
2022-06-21 9:35 Stephen Rothwell
2021-06-21 12:16 Stephen Rothwell
2020-06-21 15:23 Stephen Rothwell
2019-06-21 11:01 Stephen Rothwell
2018-06-21 4:11 Stephen Rothwell
2017-06-21 8:09 Stephen Rothwell
2015-06-21 10:50 Stephen Rothwell
2013-06-21 8:17 Stephen Rothwell
2012-06-21 6:12 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=f43656af-050c-82b3-e10d-66be072be320@mellanox.com \
--to=cmetcalf@mellanox$(echo .)com \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@kernel$(echo .)org \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sudipm.mukherjee@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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