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 theWe could keep the string in /proc/cpuinfo for compatibility but kill thecpuinfo_x86 members.-- Regards/Gruss, Boris.Good mailing practices for 400: avoid top-posting and trim the reply.