From: Timur Tabi <timur@codeaurora.org>
To: Punit Agrawal <punit.agrawal@arm.com>
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
Date: Wed, 17 May 2017 09:35:22 -0500 [thread overview]
Message-ID: <CAOZdJXVrMSUkHcsJXg+qdA=Bxt0bT5Dn5-MCUvZdSv8_8XaU-Q@mail.gmail.com> (raw)
In-Reply-To: <87lgqcy5uw.fsf@e105922-lin.cambridge.arm.com>
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?
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
WARNING: multiple messages have this Message-ID (diff)
From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64: hugetlb: Fix huge_pte_offset to return poisoned page table entries
Date: Wed, 17 May 2017 09:35:22 -0500 [thread overview]
Message-ID: <CAOZdJXVrMSUkHcsJXg+qdA=Bxt0bT5Dn5-MCUvZdSv8_8XaU-Q@mail.gmail.com> (raw)
In-Reply-To: <87lgqcy5uw.fsf@e105922-lin.cambridge.arm.com>
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?
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-05-17 14:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 14:04 [PATCH 0/3] arm64: Add support for handling memory corruption Punit Agrawal
2017-04-12 14:04 ` Punit Agrawal
2017-04-12 14:04 ` [PATCH 1/3] arm64: hugetlb: Fix huge_pte_offset to return poisoned page table entries Punit Agrawal
2017-04-12 14:04 ` Punit Agrawal
2017-04-14 19:29 ` Baicar, Tyler
2017-04-14 19:29 ` Baicar, Tyler
2017-05-03 12:49 ` Catalin Marinas
2017-05-03 12:49 ` Catalin Marinas
2017-05-04 15:55 ` Punit Agrawal
2017-05-04 15:55 ` Punit Agrawal
2017-05-17 14:35 ` Timur Tabi [this message]
2017-05-17 14:35 ` Timur Tabi
2017-05-17 15:27 ` Punit Agrawal
2017-05-17 15:27 ` Punit Agrawal
2017-04-12 14:04 ` [PATCH 2/3] arm64: hwpoison: add VM_FAULT_HWPOISON[_LARGE] handling Punit Agrawal
2017-04-12 14:04 ` Punit Agrawal
2017-04-12 14:04 ` [PATCH 3/3] arm64: kconfig: allow support for memory failure handling Punit Agrawal
2017-04-12 14:04 ` Punit Agrawal
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='CAOZdJXVrMSUkHcsJXg+qdA=Bxt0bT5Dn5-MCUvZdSv8_8XaU-Q@mail.gmail.com' \
--to=timur@codeaurora.org \
--cc=catalin.marinas@arm.com \
--cc=dwoods@mellanox.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=punit.agrawal@arm.com \
--cc=steve.capper@arm.com \
--cc=tbaicar@codeaurora.org \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.