From: Andrew Morton <akpm@linux-foundation.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Mike Rapoport <rppt@linux.ibm.com>, Will Deacon <will@kernel.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
anshuman.khandual@arm.com,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>,
lkft-triage@lists.linaro.org, suzuki.poulose@arm.com,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: Linux-next-20200302: arm64 build failed
Date: Mon, 2 Mar 2020 14:24:12 -0800 [thread overview]
Message-ID: <20200302142412.f8f2b17a3387b46ce94c7cb6@linux-foundation.org> (raw)
In-Reply-To: <20200302174553.GC4166275@arrakis.emea.arm.com>
On Mon, 2 Mar 2020 17:45:53 +0000 Catalin Marinas <catalin.marinas@arm.com> wrote:
> > static void unmap_hotplug_range(unsigned long addr, unsigned long end,
> > bool free_mapped)
> > {
> > @@ -854,7 +872,7 @@ static void unmap_hotplug_range(unsigned long addr, unsigned long end,
> > continue;
> >
> > WARN_ON(!pgd_present(pgd));
> > - unmap_hotplug_pud_range(pgdp, addr, next, free_mapped);
> > + unmap_hotplug_p4d_range(pgdp, addr, next, free_mapped);
> > } while (addr = next, addr < end);
> > }
>
> Thanks Mike. With the additional diff below, I can get it to build with
> and without the p4d clean-up patches in -next. If Anshuman confirms that
> they work, I can add them on top of the arm64 for-next/memory-hotremove
> branch
Can't I simply fold these into the offending -mm
arm-arm64-add-support-for-folded-p4d-page-tables.patch?
next prev parent reply other threads:[~2020-03-02 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 8:28 Linux-next-20200302: arm64 build failed Naresh Kamboju
2020-03-02 10:47 ` Will Deacon
2020-03-02 13:48 ` Anshuman Khandual
2020-03-02 13:54 ` Mike Rapoport
2020-03-02 17:45 ` Catalin Marinas
2020-03-02 22:24 ` Andrew Morton [this message]
2020-03-03 4:04 ` Anshuman Khandual
2020-03-03 16:28 ` Catalin Marinas
2020-03-04 2:26 ` Anshuman Khandual
2020-03-04 4:32 ` Anshuman Khandual
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=20200302142412.f8f2b17a3387b46ce94c7cb6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=rppt@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=suzuki.poulose@arm.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox