From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752755AbcCAJpj (ORCPT ); Tue, 1 Mar 2016 04:45:39 -0500 Received: from mail-wm0-f66.google.com ([74.125.82.66]:33174 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752097AbcCAJpg (ORCPT ); Tue, 1 Mar 2016 04:45:36 -0500 Date: Tue, 1 Mar 2016 10:45:32 +0100 From: Ingo Molnar To: "H. Peter Anvin" Cc: sedat.dilek@gmail.com, Stephen Rothwell , Thomas Gleixner , Ingo Molnar , Peter Zijlstra , linux-next , LKML , Josh Poimboeuf Subject: Re: linux-next: build failure after merge of the tip tree Message-ID: <20160301094531.GA23893@gmail.com> References: <20160301122910.74ff0a92@canb.auug.org.au> <20160301070750.GA6636@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * H. Peter Anvin wrote: > That is not the issue here. The problem is clearly that objtool is a host > program and not compiled with host cc. So it is a good thing to test even > though it is weird, because it affects real use cases. Absolutely, it's a real bug that should be fixed. What is counterproductive is that this rare and hard to replicate build modus is now a must-have test for linux-next inclusion. I already cross-build to 20+ weird, rarely used architectures, slowing down the linux-next merge integration test immensely and wasting quite a bit of electricity. linux-next making it even harder to test for is a step backwards. Thanks, Ingo