From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
linuxppc-dev@lists.ozlabs.org
Cc: "Michal Hocko" <mhocko@suse.com>,
linux-kernel@vger.kernel.org,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Paul Mackerras" <paulus@samba.org>,
"Joe Perches" <joe@perches.com>,
"Oliver O'Halloran" <oohall@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Vlastimil Babka" <vbabka@suse.cz>
Subject: Re: [v2, 1/5] powerpc: mm: Simplify page_is_ram by using memblock_is_memory
Date: Sun, 1 Apr 2018 01:04:11 +1100 (AEDT) [thread overview]
Message-ID: <40D0bH5b9gz9s1S@ozlabs.org> (raw)
In-Reply-To: <20180328002544.18526-2-j.neuschaefer@gmx.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
On Wed, 2018-03-28 at 00:25:40 UTC, =?utf-8?q?Jonathan_Neusch=C3=A4fer?= wrote:
> Instead of open-coding the search in page_is_ram, call memblock_is_memory.
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/2615c93e5f52db62586112793d889f
cheers
next prev parent reply other threads:[~2018-03-31 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 0:25 [PATCH v2 0/5] PPC32/ioremap: Use memblock API to check for RAM Jonathan Neuschäfer
2018-03-28 0:25 ` [PATCH v2 1/5] powerpc: mm: Simplify page_is_ram by using memblock_is_memory Jonathan Neuschäfer
2018-03-31 14:04 ` Michael Ellerman [this message]
2018-03-28 0:25 ` [PATCH v2 2/5] powerpc: mm: Use memblock API for PPC32 page_is_ram Jonathan Neuschäfer
2018-03-28 0:25 ` [PATCH v2 3/5] powerpc/mm/32: Use page_is_ram to check for RAM Jonathan Neuschäfer
2018-03-28 0:25 ` [PATCH v2 4/5] powerpc: wii: Don't rely on the reserved memory hack Jonathan Neuschäfer
2018-03-28 0:25 ` [PATCH v2 5/5] powerpc/mm/32: Remove " Jonathan Neuschäfer
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=40D0bH5b9gz9s1S@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=akpm@linux-foundation.org \
--cc=j.neuschaefer@gmx.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@suse.com \
--cc=oohall@gmail.com \
--cc=paulus@samba.org \
--cc=vbabka@suse.cz \
/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).