From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753842AbdEQP1s (ORCPT <rfc822;w@1wt.eu>);
        Wed, 17 May 2017 11:27:48 -0400
Received: from foss.arm.com ([217.140.101.70]:49202 "EHLO foss.arm.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752344AbdEQP1r (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 17 May 2017 11:27:47 -0400
From: Punit Agrawal <punit.agrawal@arm.com>
To: Timur Tabi <timur@codeaurora.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
        David Woods <dwoods@mellanox.com>, steve.capper@arm.com,
        Tyler Baicar <tbaicar@codeaurora.org>,
        Will Deacon <will.deacon@arm.com>, lkml <linux-kernel@vger.kernel.org>,
        "linux-arm-kernel\@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] arm64: hugetlb: Fix huge_pte_offset to return poisoned page table entries
References: <20170412140459.21824-1-punit.agrawal@arm.com>
        <20170412140459.21824-2-punit.agrawal@arm.com>
        <20170503124906.GA5622@e104818-lin.cambridge.arm.com>
        <87lgqcy5uw.fsf@e105922-lin.cambridge.arm.com>
        <CAOZdJXVrMSUkHcsJXg+qdA=Bxt0bT5Dn5-MCUvZdSv8_8XaU-Q@mail.gmail.com>
Date: Wed, 17 May 2017 16:27:44 +0100
In-Reply-To: <CAOZdJXVrMSUkHcsJXg+qdA=Bxt0bT5Dn5-MCUvZdSv8_8XaU-Q@mail.gmail.com>
        (Timur Tabi's message of "Wed, 17 May 2017 09:35:22 -0500")
Message-ID: <87tw4jlczz.fsf@e105922-lin.cambridge.arm.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Timur Tabi <timur@codeaurora.org> writes:

> On Thu, May 4, 2017 at 10:55 AM, Punit Agrawal <punit.agrawal@arm.com> wrote:
>> Indeed - I was avoiding changing the function to drop contiguous
>> hugepage support which follows this hunk.
>>
>> I've made changes locally based on your suggestion and will post a
>> revised version after the merge window.
>
> Punit, will you be able to post a new version that could be a
> candidate for 4.13?

Hi Timur,

I've just posted v2 for this series. I was testing the patches on rc1
when I saw your mail come through.

Please shout out if you notice any problems with the new version.

Thanks,
Punit