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  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]
Date:	Tue, 06 May 2014 09:33:42 -0700
From:	Laura Abbott <>
To:	Grant Likely <>,
	Russell King <>,
	David Brown <>,
	Daniel Walker <>,
	Jason Cooper <>,
	Andrew Lunn <>,
	Sebastian Hesselbarth <>,
	Eric Miao <>,
	Haojian Zhuang <>,
	Ben Dooks <>,
	Kukjin Kim <>,
CC:	Nicolas Pitre <>,
	Courtney Cavin <>,
	Grygorii Strashko <>,
	Ard Biesheuvel <>,, Will Deacon <>,,
	Leif Lindholm <>,,
	Catalin Marinas <>,
	Santosh Shilimkar <>,
	Andrew Morton <>,
	Marek Szyprowski <>
Subject: Re: [PATCHv5 2/2] arm: Get rid of meminfo

On 5/1/2014 6:08 AM, Grant Likely wrote:
> On Thu,  3 Apr 2014 10:04:58 -0700, Laura Abbott <> wrote:
>> memblock is now fully integrated into the kernel and is the prefered
>> method for tracking memory. Rather than reinvent the wheel with
>> meminfo, migrate to using memblock directly instead of meminfo as
>> an intermediate.
>> Change-Id: I9d04e636f43bf939e13b4934dc23da0c076811d2
>> Acked-by: Jason Cooper <>
>> Acked-by: Catalin Marinas <>
>> Acked-by: Santosh Shilimkar <>
>> Tested-by: Leif Lindholm <>
>> Signed-off-by: Laura Abbott <>
> Tested-by: Grant Likely <>
> Tiny nit-picking comment below, but this patch looks really good.
> What's the state on merging this?

I put this into the patch system as 8025/1 a few weeks ago. I've been
busy/on vacation so I haven't had a chance to follow up since then.


Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists