linux-kernel - Re: [PATCH 1/3]: Store SRAT revision

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:	Sun, 15 Jan 2012 13:52:37 -0800
From:	Greg KH <greg@...ah.com>
To:	Kurt Garloff <kurt@...loff.de>, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org, stable@...r.kernel.org, lenb@...nel.org
Subject: Re: [PATCH 1/3]: Store SRAT revision

On Sun, Jan 15, 2012 at 10:34:07PM +0100, Kurt Garloff wrote:
> Hi,
> 
> This patch stores the SRAT table revision for later consumption
> by arch specific __init functions.
> 
> 
> This is patch 1/3.
> -- 
> Kurt Garloff <kurt@...loff.de>  [Koeln/Greven]
> 

> From: Kurt Garloff <kurt@...loff.de>
> Subject: Store SRAT table revision
> References: bnc#503038
> 
> In SRAT v1, we had 8bit proximity domain (PXM) fields; SRAT v2 provides
> 32bits for these. The new fields were reserved before.
> According to the ACPI spec, the OS must disregrard reserved fields.
> In order to know whether or not, we must know what version the SRAT
> table has.
> 
> This patch stores the SRAT table revision for later consumption
> by arch specific __init functions.
> 
> This is patch 1/3.
> 
> Signed-off-by: Kurt Garloff <kurt@...loff.de>
> 
> ---
>  drivers/acpi/numa.c      |    3 +++
>  include/acpi/acpi_numa.h |    1 +
>  2 files changed, 4 insertions(+)


<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
for how to do this properly.

</formletter>
--
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/