[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a587687a-5d90-c03d-f3d2-1ea9cab1b0c4@oracle.com>
Date: Wed, 18 Oct 2017 13:23:22 -0400
From: Pavel Tatashin <pasha.tatashin@...cle.com>
To: Andrey Ryabinin <aryabinin@...tuozzo.com>,
Will Deacon <will.deacon@....com>, mhocko@...nel.org,
akpm@...ux-foundation.org
Cc: linux-kernel@...r.kernel.org, sparclinux@...r.kernel.org,
linux-mm@...ck.org, linuxppc-dev@...ts.ozlabs.org,
linux-s390@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
x86@...nel.org, kasan-dev@...glegroups.com, borntraeger@...ibm.com,
heiko.carstens@...ibm.com, davem@...emloft.net,
willy@...radead.org, ard.biesheuvel@...aro.org,
mark.rutland@....com, catalin.marinas@....com, sam@...nborg.org,
mgorman@...hsingularity.net, steven.sistare@...cle.com,
daniel.m.jordan@...cle.com, bob.picco@...cle.com
Subject: Re: [PATCH v12 08/11] arm64/kasan: add and use kasan_map_populate()
Hi Andrew and Michal,
There are a few changes I need to do to my series:
1. Replace these two patches:
arm64/kasan: add and use kasan_map_populate()
x86/kasan: add and use kasan_map_populate()
With:
x86/mm/kasan: don't use vmemmap_populate() to initialize
shadow
arm64/mm/kasan: don't use vmemmap_populate() to initialize
shadow
2. Fix a kbuild warning about section mismatch in
mm: deferred_init_memmap improvements
How should I proceed to get these replaced in mm-tree? Send three new
patches, or send a new series?
Thank you,
Pavel
On 10/18/2017 01:18 PM, Andrey Ryabinin wrote:
> On 10/18/2017 08:08 PM, Pavel Tatashin wrote:
>>>
>>> As I said, I'm fine either way, I just didn't want to cause extra work
>>> or rebasing:
>>>
>>> http://lists.infradead.org/pipermail/linux-arm-kernel/2017-October/535703.html
>>
>> Makes sense. I am also fine either way, I can submit a new patch merging together the two if needed.
>>
>
> Please, do this. Single patch makes more sense
>
>
>> Pavel
Powered by blists - more mailing lists