[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190704141358.495791a385f7dd762cb749c2@linux-foundation.org>
Date: Thu, 4 Jul 2019 14:13:58 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Robin Murphy <robin.murphy@....com>
Cc: Jason Gunthorpe <jgg@...lanox.com>,
Christoph Hellwig <hch@...radead.org>,
Mark Rutland <mark.rutland@....com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"will.deacon@....com" <will.deacon@....com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"anshuman.khandual@....com" <anshuman.khandual@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Michal Hocko <mhocko@...e.com>,
Dan Williams <dan.j.williams@...el.com>
Subject: Re: [PATCH v3 0/4] Devmap cleanups + arm64 support
On Thu, 4 Jul 2019 21:54:36 +0100 Robin Murphy <robin.murphy@....com> wrote:
> >> mm-clean-up-is_device__page-definitions.patch
> >> mm-introduce-arch_has_pte_devmap.patch
> >> arm64-mm-implement-pte_devmap-support.patch
> >> arm64-mm-implement-pte_devmap-support-fix.patch
> >
> > This one we discussed, and I thought we agreed would go to your 'stage
> > after linux-next' flow (see above). I think the conflict was minor
> > here.
>
> I can rebase and resend tomorrow if there's an agreement on what exactly
> to base it on - I'd really like to get this ticked off for 5.3 if at all
> possible.
I took another look. Yes, it looks like the repairs were simple.
Let me now try to compile all this...
Powered by blists - more mailing lists