[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dca485fe-7024-392b-f51c-cd54550317ff@redhat.com>
Date: Sun, 29 Mar 2020 21:19:13 +0200
From: David Hildenbrand <david@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: linux-mm@...ck.org,
Segher Boessenkool <segher@...nel.crashing.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Oscar Salvador <osalvador@...e.de>,
Michal Hocko <mhocko@...nel.org>, Baoquan He <bhe@...hat.com>,
Dan Williams <dan.j.williams@...el.com>,
Wei Yang <richardw.yang@...ux.intel.com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH v2 1/2] mm/memory_hotplug: simplify calculation of number
of pages in __remove_pages()
On 28.02.20 10:58, David Hildenbrand wrote:
> In commit 52fb87c81f11 ("mm/memory_hotplug: cleanup __remove_pages()"),
> we cleaned up __remove_pages(), and introduced a shorter variant to
> calculate the number of pages to the next section boundary.
>
> Turns out we can make this calculation easier to read. We always want to
> have the number of pages (> 0) to the next section boundary, starting from
> the current pfn.
@Andrew
This patch seems to have another of these weird MIME crap in it. (my
other patches in -next seem to be fine)
See
https://lore.kernel.org/linux-mm/20200228095819.10750-2-david@redhat.com/raw
"
... fro=
m"
should simply be "... from"
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists