mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Laura Abbott <lauraa@codeaurora.org>
Cc: <linux-mm@kvack.org>, Andrew Morton <akpm@linux-foundation.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>
Subject: Re: [PATCHv2 1/2] mm/memblock: add memblock_get_current_limit
Date: Wed, 5 Feb 2014 18:19:28 -0500	[thread overview]
Message-ID: <52F2C700.8070502@ti.com> (raw)
In-Reply-To: <1391558551-31395-2-git-send-email-lauraa@codeaurora.org>

On Tuesday 04 February 2014 07:02 PM, Laura Abbott 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.
> 
> Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
> ---
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>


  parent reply	other threads:[~2014-02-05 23:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05  0:02 [PATCHv2 0/2] Remove ARM meminfo Laura Abbott
2014-02-05  0:02 ` [PATCHv2 1/2] mm/memblock: add memblock_get_current_limit Laura Abbott
2014-02-05 22:01   ` Andrew Morton
2014-02-05 23:19   ` Santosh Shilimkar [this message]
2014-02-05  0:02 ` [PATCHv2 2/2] arm: Get rid of meminfo Laura Abbott
2014-02-05  2:00   ` Jason Cooper
2014-02-05 13:43   ` Leif Lindholm
2014-02-05 23:21   ` Santosh Shilimkar
2014-02-07  2:09   ` Courtney Cavin
2014-02-10  3:25     ` Laura Abbott
2014-02-10 10:11       ` Catalin Marinas
2014-02-10 17:28       ` Courtney Cavin
2014-02-10 21:59         ` Laura Abbott
2014-02-10 21:58   ` Grant Likely
2014-02-11  9:47   ` Marek Szyprowski
2014-02-05 13:55 ` [PATCHv2 0/2] Remove ARM meminfo Catalin Marinas

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=52F2C700.8070502@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=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=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

Powered by JetHome