[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1610141354090.11707@nanos>
Date: Fri, 14 Oct 2016 13:56:36 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Piotr Luc <piotr.luc@...el.com>
cc: Mauro Carvalho Chehab <mchehab@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Viresh Kumar <viresh.kumar@...aro.org>,
Doug Thompson <dougthompson@...ssion.com>,
Borislav Petkov <bp@...en8.de>, linux-edac@...r.kernel.org,
linux-kernel@...r.kernel.org, Len Brown <lenb@...nel.org>,
linux-pm@...r.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
Subject: Re: [PATCH v2 02/11] tools/power turbostat: Use Intel family processor
macros
On Thu, 13 Oct 2016, Piotr Luc wrote:
> + case INTEL_FAM6_NEHALEM_EP: /* Core i7, Xeon 5500 series - Bloomfield, Gainstown NHM-EP */
What's the point of keeping all those comments around?
> + case INTEL_FAM6_SANDYBRIDGE: /* SNB */
Especialy those, which are completely useless?
The defines are there to be self explaining and the extra verbose
information should be in the header file defining the macros and not in the
source code.
Thanks,
tglx
Powered by blists - more mailing lists