| 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
| ||
|
Message-Id: <20140205140113.f02dd196c88ad2cf55123b9e@linux-foundation.org> Date: Wed, 5 Feb 2014 14:01:13 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Laura Abbott <lauraa@...eaurora.org> Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org, Leif Lindholm <leif.lindholm@...aro.org>, Grygorii Strashko <grygorii.strashko@...com>, Catalin Marinas <catalin.marinas@....com>, Rob Herring <robherring2@...il.com>, Ard Biesheuvel <ard.biesheuvel@...aro.org>, Will Deacon <will.deacon@....com>, Nicolas Pitre <nicolas.pitre@...aro.org>, Santosh Shilimkar <santosh.shilimkar@...com> Subject: Re: [PATCHv2 1/2] mm/memblock: add memblock_get_current_limit On Tue, 4 Feb 2014 16:02:30 -0800 Laura Abbott <lauraa@...eaurora.org> wrote: > Appart from setting the limit of memblock, it's also useful to be able > to get the limit to avoid recalculating it every time. Add the function > to do so. Looks OK to me. Your "[PATCHv2 2/2] arm: Get rid of meminfo" did not make it into my inbox or into my lkml folder, but I found it at lkml.org so the server did send it. I'm not sure what's up with that. Please include [patch 1/2] within or alongside [patch 2/2] so they both get merged via the same route, which is presumably an arm tree. -- 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/
Powered by blists - more mailing lists