From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, David Hildenbrand <david@redhat.com>
Subject: [PATCH v2 0/2] mm/memory_hotplug: __add_pages() and __remove_pages() cleanups
Date: Fri, 28 Feb 2020 10:58:17 +0100 [thread overview]
Message-ID: <20200228095819.10750-1-david@redhat.com> (raw)
This is the follow up of:
"[PATCH v1] mm/memory_hotplug: Easier calculation to get pages to
next section boundary" [1]
Cleanups as a follow up on commit 52fb87c81f11 ("mm/memory_hotplug:
cleanup __remove_pages()").
v1 -> v2:
- "mm/memory_hotplug: simplify calculation of number of pages in
__remove_pages()"
-- Rephrased subject/description, but left patch as is
- "mm/memory_hotplug: cleanup __add_pages()"
-- Make the logic match the logic in __remove_pages()
[1] https://lkml.kernel.org/r/20200205135251.37488-1-david@redhat.com
David Hildenbrand (2):
mm/memory_hotplug: simplify calculation of number of pages in
__remove_pages()
mm/memory_hotplug: cleanup __add_pages()
mm/memory_hotplug.c | 21 +++++++++------------
1 file changed, 9 insertions(+), 12 deletions(-)
--
2.24.1
next reply other threads:[~2020-02-28 9:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 9:58 David Hildenbrand [this message]
2020-02-28 9:58 ` [PATCH v2 1/2] mm/memory_hotplug: simplify calculation of number of pages in __remove_pages() David Hildenbrand
2020-02-28 10:22 ` Baoquan He
2020-02-28 13:25 ` Wei Yang
2020-03-29 19:19 ` David Hildenbrand
2020-03-29 20:09 ` Linus Torvalds
2020-03-29 20:17 ` David Hildenbrand
2020-03-29 20:26 ` Linus Torvalds
2020-03-29 20:18 ` Linus Torvalds
2020-03-29 20:41 ` David Hildenbrand
2020-03-30 22:14 ` Andrew Morton
2020-03-30 22:27 ` Linus Torvalds
2020-02-28 9:58 ` [PATCH v2 2/2] mm/memory_hotplug: cleanup __add_pages() David Hildenbrand
2020-02-28 10:34 ` Baoquan He
2020-02-28 11:14 ` David Hildenbrand
2020-03-01 5:39 ` Baoquan He
2020-02-28 13:26 ` Wei Yang
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=20200228095819.10750-1-david@redhat.com \
--to=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).