Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S933395AbcLNRS5 (ORCPT <rfc822;w@1wt.eu>);
        Wed, 14 Dec 2016 12:18:57 -0500
Received: from mail-yb0-f193.google.com ([209.85.213.193]:34262 "EHLO
        mail-yb0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932306AbcLNRSy (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 14 Dec 2016 12:18:54 -0500
MIME-Version: 1.0
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Date: Wed, 14 Dec 2016 11:17:25 -0600
X-Google-Sender-Auth: cSerOzweN9MocI4IKR175PFNAwE
Message-ID: <CAB=NE6XSPhQsjXNPhfuUjjHruBvxt-EF5q4N_Lu2ndz5Uo7_qQ@mail.gmail.com>
Subject: linux-next x86 build fixes
To: Nicholas Piggin <npiggin@gmail.com>, Borislav Petkov <bp@alien8.de>
Cc: linux-next@vger.kernel.org, X86 ML <x86@kernel.org>,
        Steven Rostedt <rostedt@goodmis.org>,
        Adam Borowski <kilobyte@angband.pl>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 506
Lines: 10

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 ?

  Luis