linux-kernel - linux-next x86 build fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAB=NE6XSPhQsjXNPhfuUjjHruBvxt-EF5q4N_Lu2ndz5Uo7_qQ@mail.gmail.com>
Date:   Wed, 14 Dec 2016 11:17:25 -0600
From:   "Luis R. Rodriguez" <mcgrof@...not-panic.com>
To:     Nicholas Piggin <npiggin@...il.com>, Borislav Petkov <bp@...en8.de>
Cc:     linux-next@...r.kernel.org, X86 ML <x86@...nel.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Adam Borowski <kilobyte@...band.pl>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: linux-next x86 build fixes

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