From: Andrew Morton <akpm@linux-foundation.org>
To: Laura Abbott <lauraa@codeaurora.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Leif Lindholm <leif.lindholm@linaro.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Rob Herring <robherring2@gmail.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Will Deacon <will.deacon@arm.com>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCHv2 1/2] mm/memblock: add memblock_get_current_limit
Date: Wed, 5 Feb 2014 14:01:13 -0800 [thread overview]
Message-ID: <20140205140113.f02dd196c88ad2cf55123b9e@linux-foundation.org> (raw)
In-Reply-To: <1391558551-31395-2-git-send-email-lauraa@codeaurora.org>
On Tue, 4 Feb 2014 16:02:30 -0800 Laura Abbott <lauraa@codeaurora.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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-02-05 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1391558551-31395-1-git-send-email-lauraa@codeaurora.org>
2014-02-05 0:02 ` Laura Abbott
2014-02-05 22:01 ` Andrew Morton [this message]
2014-02-05 23:19 ` Santosh Shilimkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140205140113.f02dd196c88ad2cf55123b9e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=grygorii.strashko@ti.com \
--cc=lauraa@codeaurora.org \
--cc=leif.lindholm@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nicolas.pitre@linaro.org \
--cc=robherring2@gmail.com \
--cc=santosh.shilimkar@ti.com \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox