linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Chris Metcalf <cmetcalf@mellanox.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: linux-next: Tree for Jun 21
Date: Tue, 21 Jun 2016 19:29:18 +0200	[thread overview]
Message-ID: <20160621172918.GS30927@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160621170607.GQ30154@twins.programming.kicks-ass.net>

On Tue, Jun 21, 2016 at 07:06:07PM +0200, Peter Zijlstra wrote:
> On Tue, Jun 21, 2016 at 11:26:19AM -0400, Chris Metcalf wrote:
> > This has been true since gcc 4.x when tilepro support was first added.
> > 
> > In any case if you replace the #include <asm/unistd.h> with
> > 
> > #define __NR_FAST_cmpxchg    -1
> > #define __NR_FAST_atomic_update    -2
> > #define __NR_FAST_cmpxchg64    -3
> > 
> > that should also probably fix it, though I haven't tested it.  It probably
> > wouldn't be crazy to just put those #defines directly in tilepro's atomic.h,
> > since it's not like those fast system call numbers will ever change.

OK, I seem to have a tilepro-linux-gcc-6.1.1 build done. Lets see if I
can build me a kernel with it.

  reply	other threads:[~2016-06-21 17:30 UTC|newest]

Thread overview: 34+ 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
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 [this message]
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 --
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=20160621172918.GS30927@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=cmetcalf@mellanox.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sudipm.mukherjee@gmail.com \
    /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).