From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752324AbdBNSbE (ORCPT <rfc822;w@1wt.eu>);
        Tue, 14 Feb 2017 13:31:04 -0500
Received: from mail.skyhub.de ([78.46.96.112]:42066 "EHLO mail.skyhub.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752180AbdBNSaq (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 14 Feb 2017 13:30:46 -0500
Date: Tue, 14 Feb 2017 19:30:29 +0100
From: Borislav Petkov <bp@alien8.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Mathias Krause <minipli@googlemail.com>,
        Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        "David S. Miller" <davem@davemloft.net>,
        Jesper Nilsson <jesper.nilsson@axis.com>,
        Mikael Starvik <starvik@axis.com>,
        Geert Uytterhoeven <geert@linux-m68k.org>, x86@kernel.org,
        linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH 3/6] x86/cpu: proc - remove "wp" status line in cpuinfo
Message-ID: <20170214183029.e2jehgc5emkobszs@pd.tnic>
References: <1486933932-585-1-git-send-email-minipli@googlemail.com>
 <1486933932-585-4-git-send-email-minipli@googlemail.com>
 <3bd5980f-19fc-9eb4-477c-4786580ceafb@zytor.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <3bd5980f-19fc-9eb4-477c-4786580ceafb@zytor.com>
User-Agent: NeoMutt/20161014 (1.7.1)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Feb 14, 2017 at 10:13:22AM -0800, H. Peter Anvin wrote:
> Potential userspace breakage, which is why the line was left in the

We could keep the string in /proc/cpuinfo for compatibility but kill the
cpuinfo_x86 members.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.