Since the e3239ff92a1 commit (memblock: Rename memblock_region
to memblock_type and memblock_property to memblock_region), all
local variables of the membock_type type were renamed to 'type'.
This commit renames all remaining local variables with the
memblock_type type to the same view.

Signed-off-by: Alexander Kuleshov <kuleshovm...@gmail.com>
---
 mm/memblock.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/mm/memblock.c b/mm/memblock.c
index 87108e7..cf6b109 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -611,14 +611,14 @@ static int __init_memblock 
memblock_add_region(phys_addr_t base,
                                                int nid,
                                                unsigned long flags)
 {
-       struct memblock_type *_rgn = &memblock.memory;
+       struct memblock_type *type = &memblock.memory;
 
        memblock_dbg("memblock_add: [%#016llx-%#016llx] flags %#02lx %pF\n",
                     (unsigned long long)base,
                     (unsigned long long)base + size - 1,
                     flags, (void *)_RET_IP_);
 
-       return memblock_add_range(_rgn, base, size, nid, flags);
+       return memblock_add_range(type, base, size, nid, flags);
 }
 
 int __init_memblock memblock_add(phys_addr_t base, phys_addr_t size)
@@ -831,10 +831,10 @@ void __init_memblock __next_reserved_mem_region(u64 *idx,
                                           phys_addr_t *out_start,
                                           phys_addr_t *out_end)
 {
-       struct memblock_type *rsv = &memblock.reserved;
+       struct memblock_type *type = &memblock.reserved;
 
-       if (*idx >= 0 && *idx < rsv->cnt) {
-               struct memblock_region *r = &rsv->regions[*idx];
+       if (*idx >= 0 && *idx < type->cnt) {
+               struct memblock_region *r = &type->regions[*idx];
                phys_addr_t base = r->base;
                phys_addr_t size = r->size;
 
-- 
2.5.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to