From: Anshuman Khandual <anshuman.khandual@arm.com>
To: linux-mm@kvack.org, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
steven.price@arm.com, christophe.leroy@csgroup.eu,
gerald.schaefer@linux.ibm.com, vgupta@synopsys.com,
paul.walmsley@sifive.com
Subject: Re: [PATCH V2 0/2] mm/debug_vm_pgtable: Some minor updates
Date: Wed, 9 Dec 2020 08:11:13 +0530 [thread overview]
Message-ID: <5ac12290-536d-968c-1ca6-10918403bb8f@arm.com> (raw)
In-Reply-To: <1606825169-5229-1-git-send-email-anshuman.khandual@arm.com>
On 12/1/20 5:49 PM, Anshuman Khandual wrote:
> This series contains some cleanups and new test suggestions from Catalin
> from an earlier discussion.
>
> https://lore.kernel.org/linux-mm/20201123142237.GF17833@gaia/
>
> This series is based on v5.10-rc6 and has been tested on arm64 and x86 but
> has only been build tested on riscv, s390, arc etc. It would be great if
> folks could test this on these platforms as well. Thank you.
>
> Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
> Cc: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
> Cc: Vineet Gupta <vgupta@synopsys.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Paul Walmsley <paul.walmsley@sifive.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
Hello Gerald/Christophe/Vineet/Paul,
Could you please give this series a quick test on s390, ppc, arc,
and riscv platforms. Thank you.
- Anshuman
next prev parent reply other threads:[~2020-12-09 2:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 12:19 Anshuman Khandual
2020-12-01 12:19 ` [PATCH V2 1/2] mm/debug_vm_pgtable/basic: Add validation for dirtiness after write protect Anshuman Khandual
2020-12-02 11:16 ` Steven Price
2020-12-02 12:04 ` Anshuman Khandual
2020-12-01 12:19 ` [PATCH V2 2/2] mm/debug_vm_pgtable/basic: Iterate over entire protection_map[] Anshuman Khandual
2020-12-09 2:41 ` Anshuman Khandual [this message]
2020-12-09 15:25 ` [PATCH V2 0/2] mm/debug_vm_pgtable: Some minor updates Gerald Schaefer
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=5ac12290-536d-968c-1ca6-10918403bb8f@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=gerald.schaefer@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paul.walmsley@sifive.com \
--cc=steven.price@arm.com \
--cc=vgupta@synopsys.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