[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140222194303.GB12698@thin>
Date: Sat, 22 Feb 2014 11:43:04 -0800
From: Josh Triplett <josh@...htriplett.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Andi Kleen <ak@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Borislav Petkov <bp@...e.de>, Feng Tang <feng.tang@...el.com>,
Ingo Molnar <mingo@...hat.com>,
Jacob Shin <jacob.shin@....com>,
Jan Beulich <JBeulich@...e.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Peter Zijlstra <peterz@...radead.org>,
Qiaowei Ren <qiaowei.ren@...el.com>,
Rob Landley <rob@...dley.net>,
Seiji Aguchi <seiji.aguchi@....com>,
Stephane Eranian <eranian@...gle.com>,
Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Thomas Renninger <trenn@...e.de>, linux-kernel@...r.kernel.org,
x86@...nel.org
Subject: Re: [PATCH 2/2] x86: Support compiling out human-friendly processor
feature names
On Sat, Feb 22, 2014 at 11:19:18AM -0800, H. Peter Anvin wrote:
> Also, for the numeric message at least please show it in word:bit format.
I can do that, but the only obvious way I see to do so (without adding
ifdefs to arch/x86/kernel/cpu/common.c) would require making
x86_cap_flag a macro generating two printk arguments. Doing so in v2;
hope that isn't too ugly...
- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists