linux-kernel - Re: [PATCH] x86: Use memblock_set_current

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] [day] [month] [year] [list]

Message-ID: <520B236D.7030704@iki.fi>
Date:	Wed, 14 Aug 2013 09:27:57 +0300
From:	Pekka Enberg <penberg@....fi>
To:	Tang Chen <tangchen@...fujitsu.com>
CC:	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	yinghai@...nel.org, jacob.shin@....com, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Use memblock_set_current_limit() to set limit for
 memblock.

On 8/14/13 6:44 AM, Tang Chen wrote:
> In setup_arch() of x86, it set memblock.current_limit directly.
> We should use memblock_set_current_limit(). If the implementation
> is changed, it is easy to maintain.
>
> Signed-off-by: Tang Chen <tangchen@...fujitsu.com>

Reviewed-by: Pekka Enberg <penberg@...nel.org>
--
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/