linux-kernel - Re: [PATCH v3 0/3] x86: devicetree: re-enable x86-specific implementation

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-prev] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.1803021011160.1803@nanos.tec.linutronix.de>
Date:   Fri, 2 Mar 2018 10:18:46 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Ivan Gorinov <ivan.gorinov@...el.com>
cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH v3 0/3] x86: devicetree: re-enable x86-specific
 implementation

On Thu, 1 Mar 2018, Ivan Gorinov wrote:

> Fixing x86-specific DT implementation in the kernel allows reusing most of
> firmware code for SoC that have ARM core replaced with x86, e.g. SC9853i.
> 
> Changes since v2:
> 
>  * WARN_ON_ONCE instead of WARN_ON to aviod multiple warnings
>    when APIC ID is missing in CPU device tree nodes
> 
>  * Switched to Mutt because of white space issues:
>    "Preformatted" paragraph style does not work in Evolution 3.18.5.2

The patches can be applied now, but still the series is not threaded. That
means 1/3 - 3/3 lack a References: tag which contains the message-id of
0/3. Please figure out how to do that, it's annoying if patch series cannot
be collapsed.

Thanks,

	tglx