From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, rppt@kernel.org,
david@redhat.com, bhe@redhat.com
Subject: [PATCH v4 0/4] mm: clean up names and parameters of memmap_init_xxxx functions
Date: Wed, 20 Jan 2021 12:52:09 +0800 [thread overview]
Message-ID: <20210120045213.6571-1-bhe@redhat.com> (raw)
This patchset is correcting inappropriate function names of
memmap_init_xxx, and simplify parameters of functions in the code flow
when I tried to fix a regression bug in memmap defer init.
This is based on the latest next/master.
v3 can be found here:
https://lore.kernel.org/linux-mm/20210105074708.18483-1-bhe@redhat.com/
v3->v4:
- Rebased patch 1, 2 on top of Mike's below new patch.
[PATCH v3 0/2] mm: fix initialization of struct page for holes in memory layout
- Move the code of renaming function parameter 'range_start_pfn' and local
variable 'range_end_pfn' of memmap_init() from patch 1 to patch 2
according to David's comment.
- Use the reverse Christmas tree style to reorder the local variables
in memmap_init_zone() in patch 2 accodrding to David's comment.
Baoquan He (4):
mm: rename memmap_init() and memmap_init_zone()
mm: simplify parater of function memmap_init_zone()
mm: simplify parameter of setup_usemap()
mm: remove unneeded local variable in free_area_init_core
arch/ia64/include/asm/pgtable.h | 3 +--
arch/ia64/mm/init.c | 14 +++++-----
include/linux/mm.h | 2 +-
mm/memory_hotplug.c | 2 +-
mm/page_alloc.c | 46 ++++++++++++++-------------------
5 files changed, 31 insertions(+), 36 deletions(-)
--
2.17.2
next reply other threads:[~2021-01-20 4:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 4:52 Baoquan He [this message]
2021-01-20 4:52 ` [PATCH v4 1/4] mm: rename memmap_init() and memmap_init_zone() Baoquan He
2021-01-20 15:47 ` kernel test robot
2021-01-20 15:47 ` kernel test robot
2021-01-21 8:17 ` Baoquan He
2021-01-21 8:17 ` Baoquan He
2021-01-21 8:25 ` Mike Rapoport
2021-01-21 8:25 ` Mike Rapoport
2021-01-21 8:43 ` Baoquan He
2021-01-21 8:43 ` Baoquan He
2021-01-22 7:13 ` Baoquan He
2021-01-22 7:13 ` Baoquan He
2021-01-22 8:46 ` David Hildenbrand
2021-01-20 4:52 ` [PATCH v4 2/4] mm: simplify parater of function memmap_init_zone() Baoquan He
2021-01-22 8:43 ` David Hildenbrand
2021-01-20 4:52 ` [PATCH v4 3/4] mm: simplify parameter of setup_usemap() Baoquan He
2021-01-20 4:52 ` [PATCH v4 4/4] mm: remove unneeded local variable in free_area_init_core Baoquan He
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=20210120045213.6571-1-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.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.