From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 5/6] ARM, mm: change meaning of max_low_pfn to maximum pfn for nobootmem
Date: Tue, 2 Jul 2013 13:38:20 -0400 [thread overview]
Message-ID: <51D3100C.6010209@ti.com> (raw)
In-Reply-To: <20130701170941.GC24642@n2100.arm.linux.org.uk>
On Monday 01 July 2013 01:09 PM, Russell King - ARM Linux wrote:
> On Mon, Jul 01, 2013 at 10:14:45AM -0400, Santosh Shilimkar wrote:
>> I have been also carrying similar patch as yours in an attempt
>> to make LPAE kernel work on ARM. Your patch carries better
>> description, so will your version and include in my series
>> which I plan to post on the list after some more testing.
>> Will copy you. The changes are very similar to your series.
>
> And will you try to investigate and/or address my concerns with this
> change?
>
Sure. Will try to look and come back to you.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Will Deacon <will.deacon@arm.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Nicolas Pitre <nico@linaro.org>
Subject: Re: [RFC PATCH 5/6] ARM, mm: change meaning of max_low_pfn to maximum pfn for nobootmem
Date: Tue, 2 Jul 2013 13:38:20 -0400 [thread overview]
Message-ID: <51D3100C.6010209@ti.com> (raw)
In-Reply-To: <20130701170941.GC24642@n2100.arm.linux.org.uk>
On Monday 01 July 2013 01:09 PM, Russell King - ARM Linux wrote:
> On Mon, Jul 01, 2013 at 10:14:45AM -0400, Santosh Shilimkar wrote:
>> I have been also carrying similar patch as yours in an attempt
>> to make LPAE kernel work on ARM. Your patch carries better
>> description, so will your version and include in my series
>> which I plan to post on the list after some more testing.
>> Will copy you. The changes are very similar to your series.
>
> And will you try to investigate and/or address my concerns with this
> change?
>
Sure. Will try to look and come back to you.
Regards,
Santosh
next prev parent reply other threads:[~2013-07-02 17:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 4:11 [RFC PATCH 0/6] ARM: use NO_BOOTMEM on default configuration Joonsoo Kim
2013-03-25 4:11 ` Joonsoo Kim
2013-03-25 4:11 ` [RFC PATCH 1/6] ARM, TCM: initialize TCM in paging_init(), instead of setup_arch() Joonsoo Kim
2013-03-25 4:11 ` Joonsoo Kim
2013-03-25 21:18 ` Linus Walleij
2013-03-25 21:18 ` Linus Walleij
2013-03-25 4:11 ` [RFC PATCH 2/6] ARM, crashkernel: use ___alloc_bootmem_node_nopanic() for reserving memory Joonsoo Kim
2013-03-25 4:11 ` Joonsoo Kim
2013-03-25 4:11 ` [RFC PATCH 3/6] ARM, crashkernel: correct total_mem size in reserve_crashkernel() Joonsoo Kim
2013-03-25 4:11 ` Joonsoo Kim
2013-03-25 4:11 ` [RFC PATCH 4/6] ARM, mm: don't do arm_bootmem_init() if CONFIG_NO_BOOTMEM Joonsoo Kim
2013-03-25 4:11 ` Joonsoo Kim
2013-03-25 4:11 ` [RFC PATCH 5/6] ARM, mm: change meaning of max_low_pfn to maximum pfn for nobootmem Joonsoo Kim
2013-03-25 4:11 ` Joonsoo Kim
2013-03-25 9:48 ` Russell King - ARM Linux
2013-03-25 9:48 ` Russell King - ARM Linux
2013-04-01 8:28 ` Joonsoo Kim
2013-04-01 8:28 ` Joonsoo Kim
2013-07-01 14:14 ` Santosh Shilimkar
2013-07-01 14:14 ` Santosh Shilimkar
2013-07-01 17:09 ` Russell King - ARM Linux
2013-07-01 17:09 ` Russell King - ARM Linux
2013-07-02 17:38 ` Santosh Shilimkar [this message]
2013-07-02 17:38 ` Santosh Shilimkar
2013-07-02 1:28 ` Joonsoo Kim
2013-07-02 1:28 ` Joonsoo Kim
2013-03-25 4:11 ` [RFC PATCH 6/6] ARM, mm: enable NO_BOOTMEM for default ARM build Joonsoo Kim
2013-03-25 4:11 ` Joonsoo Kim
2013-04-22 8:22 ` [RFC PATCH 0/6] ARM: use NO_BOOTMEM on default configuration Joonsoo Kim
2013-04-22 8:22 ` Joonsoo Kim
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=51D3100C.6010209@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.