[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181221161255.GF1325@zn.tnic>
Date: Fri, 21 Dec 2018 17:12:55 +0100
From: Borislav Petkov <bp@...en8.de>
To: Dave Hansen <dave.hansen@...el.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
linux-kernel@...r.kernel.org, x86@...nel.org,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Jia Zhang <qianyue.zj@...baba-inc.com>,
"Gustavo A. R. Silva" <garsilva@...eddedor.com>
Subject: Re: [PATCH] x86/cpu: sort cpuinfo flags
On Fri, Dec 21, 2018 at 07:19:06AM -0800, Dave Hansen wrote:
> /proc/cpuinfo is supposed to be human-readable. But, the flags field,
> as it stands, is not. You've further proved my point by having to
> machine post-process it to make it usable by humans. :)
No, it is usable now as it is. *You* claimed it isn't and I showed you
that you can sort this thing without adding code to the kernel, so that
you can have it sorted too, without the need to add more useless code to
the kernel.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists