From: Chintan Pandya <cpandya@codeaurora.org>
To: Marc Zyngier <marc.zyngier@arm.com>,
catalin.marinas@arm.com, will.deacon@arm.com,
mark.rutland@arm.com, toshi.kani@hpe.com
Cc: arnd@arndb.de, ard.biesheuvel@linaro.org, james.morse@arm.com,
kristina.martsenko@arm.com, takahiro.akashi@linaro.org,
gregkh@linuxfoundation.org, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH v8 0/4] Fix issues with huge mapping in ioremap for ARM64
Date: Tue, 3 Apr 2018 17:25:29 +0530 [thread overview]
Message-ID: <0229cecc-18fc-c3ef-a5cb-be3f9829cad4@codeaurora.org> (raw)
In-Reply-To: <a613f834-f356-a826-526f-aef532f62951@arm.com>
On 4/3/2018 2:13 PM, Marc Zyngier wrote:
> Hi Chintan,
Hi Marc,
>
> On 03/04/18 09:00, Chintan Pandya wrote:
>> This series of patches are follow up work (and depends on)
>> Toshi Kani <toshi.kani@hpe.com>'s patches "fix memory leak/
>> panic in ioremap huge pages".
>>
>> This series of patches are tested on 4.9 kernel with Cortex-A75
>> based SoC.
>
> Given that this is targeting mainline, can you please test with 4.16?
> Basing your patches on something that is over 15 months old is not
> exactly reassuring.
We have 4.14 ported with the devices (remotely) accessible to me. If
that's sufficient, I will post test report by tomorrow.
If we really require these patches to be tested with 4.16, I would need
some help here.
Thanks,
>
> Thanks,
>
> M.
>
Chintan
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center,
Inc. is a member of the Code Aurora Forum, a Linux Foundation
Collaborative Project
next prev parent reply other threads:[~2018-04-03 11:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 8:00 [PATCH v8 0/4] Fix issues with huge mapping in ioremap for ARM64 Chintan Pandya
2018-04-03 8:00 ` Chintan Pandya
2018-04-03 8:00 ` [PATCH v8 1/4] ioremap: Update pgtable free interfaces with addr Chintan Pandya
2018-04-03 8:00 ` Chintan Pandya
2018-04-03 8:00 ` [PATCH v8 2/4] arm64: tlbflush: Introduce __flush_tlb_kernel_pgtable Chintan Pandya
2018-04-03 8:00 ` Chintan Pandya
2018-04-27 10:29 ` Catalin Marinas
2018-04-27 10:29 ` Catalin Marinas
2018-04-27 12:30 ` Chintan Pandya
2018-04-27 12:30 ` Chintan Pandya
2018-04-03 8:00 ` [PATCH v8 3/4] arm64: Implement page table free interfaces Chintan Pandya
2018-04-03 8:00 ` Chintan Pandya
2018-04-03 8:00 ` [PATCH v8 4/4] Revert "arm64: Enforce BBM for huge IO/VMAP mappings" Chintan Pandya
2018-04-03 8:00 ` Chintan Pandya
2018-04-03 8:43 ` [PATCH v8 0/4] Fix issues with huge mapping in ioremap for ARM64 Marc Zyngier
2018-04-03 8:43 ` Marc Zyngier
2018-04-03 11:55 ` Chintan Pandya [this message]
2018-04-03 11:55 ` Chintan Pandya
2018-04-05 9:09 ` Chintan Pandya
2018-04-05 9:09 ` Chintan Pandya
2018-04-17 10:25 ` Chintan Pandya
2018-04-17 10:25 ` Chintan Pandya
2018-04-27 10:27 ` Catalin Marinas
2018-04-27 10:27 ` Catalin Marinas
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=0229cecc-18fc-c3ef-a5cb-be3f9829cad4@codeaurora.org \
--to=cpandya@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=kristina.martsenko@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=takahiro.akashi@linaro.org \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hpe.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox