From: Peter Zijlstra <peterz@infradead.org>
To: Chris Metcalf <cmetcalf@mellanox.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
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: Wed, 22 Jun 2016 23:05:59 +0200 [thread overview]
Message-ID: <20160622210559.GX30909@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <cea1e8b0-f0ca-7985-39f5-b66cfed50a9a@mellanox.com>
On Wed, Jun 22, 2016 at 04:43:15PM -0400, Chris Metcalf wrote:
> It turns out there were a few places where we were #include'ing Linux
> headers in the gcc build (asm/unistd.h, arch/icache.h, arch/spr_def.h).
> I patched gcc to provide inline copies of what was needed (pretty simple
> stuff and won't ever change) and asked our lead compiler guy to upstream
> it back up to gcc, so using buildall.git should get easier for tilepro/tilegx.
tilegx actually built without issue (although I think it needed
--disable-gdb for binutils).
But thanks! Much appreciated.
I'll try and make a few patches for Segher to update buildall and reduce
the number of hacks/patches I have to carry around on that.
next prev parent reply other threads:[~2016-06-22 21:06 UTC|newest]
Thread overview: 45+ 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:08 ` Chris Metcalf
2016-06-21 12:42 ` Peter Zijlstra
2016-06-21 13:47 ` Chris Metcalf
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:14 ` Peter Zijlstra
2016-06-21 14:20 ` Chris Metcalf
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 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: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 20:43 ` Chris Metcalf
2016-06-22 21:05 ` Peter Zijlstra [this message]
2016-06-22 9:16 ` Peter Zijlstra
2016-06-22 20:40 ` Chris Metcalf
2016-06-22 20:40 ` Chris Metcalf
2016-06-24 8:58 ` [tip:locking/arch-atomic] locking/atomic, arch/tile: Fix tilepro build tip-bot for Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2024-06-21 18:36 linux-next: Tree for Jun 21 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
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=20160622210559.GX30909@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.