From: Catalin Marinas <catalin.marinas@arm.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Will Deacon <will.deacon@arm.com>,
Stephen Bates <sbates@raithlin.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH 2/2] arm64: mm: make use of new memblocks_present() helper
Date: Mon, 21 Jan 2019 17:34:55 +0000 [thread overview]
Message-ID: <20190121173455.GI29504@arrakis.emea.arm.com> (raw)
In-Reply-To: <e272894e-31b6-2698-b6f5-5321b6853263@deltatee.com>
On Thu, Jan 10, 2019 at 09:51:52AM -0700, Logan Gunthorpe wrote:
> On 2019-01-10 7:15 a.m., Will Deacon wrote:
> > On Wed, Jan 09, 2019 at 01:21:00PM -0700, Logan Gunthorpe wrote:
> >> Cleanup the arm64_memory_present() function seeing it's very
> >> similar to other arches.
> >>
> >> memblocks_present() is a direct replacement of arm64_memory_present()
> >>
> >> Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
> >> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
> >> Cc: Will Deacon <will.deacon@arm.com>
> >> ---
> >> arch/arm64/mm/init.c | 20 +-------------------
> >> 1 file changed, 1 insertion(+), 19 deletions(-)
> >
> > Acked-by: Will Deacon <will.deacon@arm.com>
> >
> > Did you want us to take this via the arm64 tree?
>
> Yes please.
Patch 2/2 queued for 5.1. Thanks.
--
Catalin
prev parent reply other threads:[~2019-01-21 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 20:20 [PATCH 0/2] Cleanup ARM arches to use common memblocks_present Logan Gunthorpe
2019-01-09 20:20 ` [PATCH 1/2] ARM: mm: make use of new memblocks_present() helper Logan Gunthorpe
2019-01-09 20:21 ` [PATCH 2/2] arm64: " Logan Gunthorpe
2019-01-10 14:15 ` Will Deacon
2019-01-10 16:51 ` Logan Gunthorpe
2019-01-21 17:34 ` Catalin Marinas [this message]
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=20190121173455.GI29504@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=logang@deltatee.com \
--cc=sbates@raithlin.com \
--cc=will.deacon@arm.com \
/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).