linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@oracle.com (santosh shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] ARM: keystone2: rename init_meminfo to pv_fixup
Date: Mon, 13 Apr 2015 12:03:41 -0700	[thread overview]
Message-ID: <552C130D.8000804@oracle.com> (raw)
In-Reply-To: <E1YfmY0-0006Wz-Tz@rmk-PC.arm.linux.org.uk>

On 4/8/2015 2:45 AM, Russell King wrote:
> The init_meminfo() method is not about initialising meminfo - it's about
> fixing up the physical to virtual translation so that we use a different
> physical address space, possibly above the 4GB physical address space.
> Therefore, the name "init_meminfo()" is confusing.
>
Indeed.

> Rename it to pv_fixup() instead.
>
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
> ---
Acked-by: Santosh Shilimkar <ssantosh@kernel.org>

  reply	other threads:[~2015-04-13 19:03 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08  9:44 [PATCH 0/7] Fix Keystone 2 physical address switch Russell King - ARM Linux
2015-04-08  9:45 ` [PATCH 1/6] ARM: keystone2: move platform notifier initialisation into platform init Russell King
2015-04-13 18:57   ` santosh shilimkar
2015-04-08  9:45 ` [PATCH 2/6] ARM: keystone2: move update of the phys-to-virt constants into generic code Russell King
2015-04-08 14:56   ` Grygorii.Strashko@linaro.org
2015-04-08 18:00     ` Russell King - ARM Linux
2015-04-09 14:51       ` Grygorii.Strashko@linaro.org
2015-04-09 15:49         ` Russell King - ARM Linux
2015-04-09 16:15           ` Grygorii.Strashko@linaro.org
2015-04-08 19:19     ` Russell King - ARM Linux
2015-04-13 19:02   ` santosh shilimkar
2015-04-08  9:45 ` [PATCH 3/6] ARM: keystone2: move address space switch printk to " Russell King
2015-04-13 19:02   ` santosh shilimkar
2015-04-08  9:45 ` [PATCH 4/6] ARM: keystone2: rename init_meminfo to pv_fixup Russell King
2015-04-13 19:03   ` santosh shilimkar [this message]
2015-04-08  9:45 ` [PATCH 5/6] ARM: re-implement physical address space switching Russell King
2015-04-08 14:34   ` Thomas Petazzoni
2015-04-08 17:27     ` santosh shilimkar
2015-04-08 18:10     ` Russell King - ARM Linux
2015-04-08 17:36   ` Mark Rutland
2015-04-08 17:55     ` Russell King - ARM Linux
2015-04-13 19:11       ` santosh shilimkar
2015-04-15 12:07         ` Mark Rutland
2015-04-15 17:27           ` santosh shilimkar
2015-04-23 11:24             ` Mark Rutland
2015-05-06 10:18               ` Russell King - ARM Linux
2015-05-06 10:37                 ` Mark Rutland
2015-05-06 11:33                   ` Russell King - ARM Linux
2015-05-06 15:33                     ` Mark Rutland
2015-05-06 15:50                       ` Russell King - ARM Linux
2015-05-06 16:14                         ` Mark Rutland
2015-05-06 16:24                           ` Will Deacon
2015-04-08  9:45 ` [PATCH 6/6] ARM: cleanup early_paging_init() calling Russell King
2015-04-13 19:13   ` santosh shilimkar
2015-04-08 17:21 ` [PATCH 0/7] Fix Keystone 2 physical address switch santosh shilimkar
2015-04-09 16:21   ` Russell King - ARM Linux
2015-04-09 16:35     ` 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=552C130D.8000804@oracle.com \
    --to=santosh.shilimkar@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).