Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756783AbcLNUms (ORCPT ); Wed, 14 Dec 2016 15:42:48 -0500 Received: from ozlabs.org ([103.22.144.67]:49125 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753022AbcLNUmf (ORCPT ); Wed, 14 Dec 2016 15:42:35 -0500 Date: Thu, 15 Dec 2016 07:41:51 +1100 From: Stephen Rothwell To: "Luis R. Rodriguez" Cc: Nicholas Piggin , Borislav Petkov , linux-next@vger.kernel.org, X86 ML , Steven Rostedt , Adam Borowski , "linux-kernel@vger.kernel.org" Subject: Re: linux-next x86 build fixes Message-ID: <20161215074151.2412ddb8@canb.auug.org.au> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 741 Lines: 19 Hi Luis, On Wed, 14 Dec 2016 11:17:25 -0600 "Luis R. Rodriguez" wrote: > > Curious if the x86 symbol build issues are supposed to be resolved > already on linux-next as of today, if not, how's it looking to get > this fixed ? I am carrying around Adam's temporary patch "kbuild: > provide include/asm/asm-prototypes.h for x86" on top of linux-next but > each day I move on I keep seeing this is still not fixed and keep > having to carry it. Curious what the delays are to get this resolved, > the last thread I saw seemed to acknowledge the issue and that Nick > was working on a fix ? That commit will be in linux-next today (it was added to the kbuild tree last night (my time)). -- Cheers, Stephen Rothwell