lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 03 Jun 2016 02:38:59 +0200
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Dave Hansen <dave@...1.net>
Cc:	linux-kernel@...r.kernel.org, x86@...nel.org,
	jacob.jun.pan@...el.com, dave.hansen@...ux.intel.com,
	adrian.hunter@...el.com, ak@...ux.intel.com, luto@...nel.org,
	bp@...en8.de, dvhart@...radead.org, dougthompson@...ssion.com,
	edubezval@...il.com, hpa@...or.com, mingo@...hat.com,
	jacob.jun.pan@...ux.intel.com, kan.liang@...el.com,
	lenb@...nel.org, linux-acpi@...r.kernel.org,
	linux-edac@...r.kernel.org, linux-mmc@...r.kernel.org,
	linux-pm@...r.kernel.org, mchehab@....samsung.com,
	peterz@...radead.org, platform-driver-x86@...r.kernel.org,
	rafael.j.wysocki@...el.com, rajneesh.bhardwaj@...el.com,
	souvik.k.chakravarty@...el.com,
	srinivas.pandruvada@...ux.intel.com, eranian@...gle.com,
	tglx@...utronix.de, tony.luck@...el.com, ulf.hansson@...aro.org,
	viresh.kumar@...aro.org, vishwanath.somayaji@...el.com,
	rui.zhang@...el.com
Subject: Re: [PATCH 01/20] [v2] x86, intel: Introduce macros for Intel family numbers

On Thursday, June 02, 2016 05:19:27 PM Dave Hansen wrote:
> 
> Changes from v1:
>  * added acks from a few folks
>  * Took the redundant "MODEL_" out of the macro names (Suggested
>    by Borislav Petkov and acked by others)
> 
> From: Dave Hansen <dave.hansen@...ux.intel.com>
> 
> If you are cc'd on this code, please check _your_ code vs. the
> model list in "intel-family.h".  Please make sure you have all
> the models listed that you intend to.
> 
> Also, rather than trickling these in via all the various
> maintainers, should these just get pulled in to the x86 tree in
> one go?

Yes, please.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ