From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753750AbcGZGiX (ORCPT ); Tue, 26 Jul 2016 02:38:23 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:33345 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752518AbcGZGiW (ORCPT ); Tue, 26 Jul 2016 02:38:22 -0400 Date: Tue, 26 Jul 2016 08:38:17 +0200 From: Ingo Molnar To: Stephen Rothwell Cc: Linus Torvalds , Linux Kernel Mailing List , Peter Zijlstra , Arnaldo Carvalho de Melo , Jiri Olsa , Thomas Gleixner , Andrew Morton Subject: Re: [GIT PULL] perf changes for v4.8 Message-ID: <20160726063817.GA17368@gmail.com> References: <20160725082838.GA16210@gmail.com> <20160725235330.07c231a3@canb.auug.org.au> <20160725151520.GA5030@gmail.com> <20160725153536.GA5715@gmail.com> <20160726072123.497240f2@canb.auug.org.au> <20160726075903.18bcef41@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160726075903.18bcef41@canb.auug.org.au> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Stephen Rothwell wrote: > Hi Linus, > > On Mon, 25 Jul 2016 14:45:53 -0700 Linus Torvalds wrote: > > > > On Mon, Jul 25, 2016 at 2:21 PM, Stephen Rothwell wrote: > > > > > > Actually, the perf tree on its own was enough to trigger the build > > > problem, the luto-next tree was just what initially triggered the build > > > failure in linux-next (I guess there is some missing dependency). > > > After the build failed, I started including the perf tree directly > > > before the tip tree and the build would fail when I merged that ... > > > > Ugh. It's merged in my tree now, because I thought it was ok. Can > > somebody point me to the fix? > > I only affects cross building of the objtool and vdso2c tools (which is > how I work). The latest version of the perf/core branch in the tip > tree now has all the fixes, so I assume that Ingo will send another > pull request. Yes, I'll send this ASAP. > Unfortunately, that means that your tree is broken for me this > morning ... but I will cope, I guess. That's weird, I pushed out the fix from Arnaldo yesterday (about 8 hours ago) which should merge fine with Linus's tree and make your tooling combination work. Thanks, Ingo