[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56A66D28.1080204@redhat.com>
Date: Mon, 25 Jan 2016 10:44:56 -0800
From: Laura Abbott <labbott@...hat.com>
To: mika.penttila@...tfour.com, linux-kernel@...r.kernel.org
Cc: linux-mm@...ck.org, rientjes@...gle.com, linux@....linux.org.uk,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 3/4] arm64: let set_memory_xx(addr, 0) succeed.
On 01/23/2016 07:05 AM, mika.penttila@...tfour.com wrote:
> From: Mika Penttilä <mika.penttila@...tfour.com>
>
> This makes set_memory_xx() consistent with x86.
>
> Signed-off-by: Mika Penttilä mika.penttila@...tfour.com
>
> ---
> arch/arm64/mm/pageattr.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm64/mm/pageattr.c b/arch/arm64/mm/pageattr.c
> index 3571c73..52220dd 100644
> --- a/arch/arm64/mm/pageattr.c
> +++ b/arch/arm64/mm/pageattr.c
> @@ -51,6 +51,9 @@ static int change_memory_common(unsigned long addr, int numpages,
> WARN_ON_ONCE(1);
> }
>
> + if (!numpages)
> + return 0;
> +
> if (start < MODULES_VADDR || start >= MODULES_END)
> return -EINVAL;
>
>
I think this is going to conflict with Ard's patch
lkml.kernel.org/g/<1453125665-26627-1-git-send-email-ard.biesheuvel@...aro.org>
Can you rebase on top of that?
Thanks,
Laura
Powered by blists - more mailing lists