From: Will Deacon <will@kernel.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: song.bao.hua@hisilicon.com, sfr@canb.auug.org.au,
clang-built-linux@googlegroups.com,
Nick Desaulniers <ndesaulniers@google.com>,
linuxarm@huawei.com, ardb@kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, guro@fb.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: arm64: mm: move dma_contiguous_reserve() to be after paging_init()
Date: Thu, 17 Sep 2020 10:02:35 +0100 [thread overview]
Message-ID: <20200917090234.GB29556@willie-the-truck> (raw)
In-Reply-To: <ccfcf5a5-79d1-6339-b4b8-33b587507807@oracle.com>
Hi Mike,
On Wed, Sep 16, 2020 at 05:27:18PM -0700, Mike Kravetz wrote:
> On 9/16/20 5:19 PM, Nick Desaulniers wrote:
> > It looks like that change referenced may also break arm32 boots with today's
> > next?
> >
> > The following allows me to boot, but I have no idea if it's incorrect or not.
>
> Thanks Nick,
>
> The referenced commit was pulled from Andrew's tree and subsequent versions
> of next.
By "pulled" do you mean removed? (potential terminology clash with git pull
is confusing me here!).
> I'm looking into other architectures as this is dependent on where in arch
> specific boot process first cma call is made. Hopefully, there is a some
> way to do this without potentially touching a bunch of arch code.
Ok, for now I won't queue this arm64 patch, then.
Cheers,
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-17 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 8:59 [PATCH] arm64: mm: move dma_contiguous_reserve() to be after paging_init() Barry Song
2020-09-16 15:12 ` Anders Roxell
2020-09-17 0:19 ` Nick Desaulniers
2020-09-17 0:27 ` Mike Kravetz
2020-09-17 1:35 ` Song Bao Hua (Barry Song)
2020-09-17 9:02 ` Will Deacon [this message]
2020-09-17 9:13 ` Stephen Rothwell
2020-09-17 9:36 ` Will Deacon
2020-09-17 0:57 ` Song Bao Hua (Barry Song)
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=20200917090234.GB29556@willie-the-truck \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=guro@fb.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linuxarm@huawei.com \
--cc=mike.kravetz@oracle.com \
--cc=ndesaulniers@google.com \
--cc=sfr@canb.auug.org.au \
--cc=song.bao.hua@hisilicon.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).