From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Sarthak Sharma <sarthak.sharma@arm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
"Liam R . Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@suse.com>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Shuah Khan <shuah@kernel.org>,
John Hubbard <jhubbard@nvidia.com>,
Kalesh Singh <kaleshsingh@google.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Park Tae-sun <ts930@dgu.ac.kr>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2 00/12] improve mremap_test
Date: Mon, 16 Nov 2026 15:51:44 +0000 [thread overview]
Message-ID: <avsmKAf4MRwGdpGI@gremlin> (raw)
In-Reply-To: <20261102100211.141831-1-sarthak.sharma@arm.com>
Hi Sarthak,
Sorry we're being slow on this one, right now mm is really inundated with stuff
so we're in firefighting mode (see [0]), so I'm not sure if we'll have time to
get back to this this cycle, will try to if I'm able to! :)
--
Cheers, Lorenzo
[0]: https://lore.kernel.org/linux-mm/a2f584f6-e382-4876-aa6d-d5a34de6ee59@kernel.org/
prev parent reply other threads:[~2026-11-16 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 10:01 [PATCH RESEND v2 00/12] improve mremap_test Sarthak Sharma
2026-11-02 10:02 ` [PATCH RESEND v2 01/12] selftests/mm: mremap_test: remove command line options Sarthak Sharma
2026-11-02 10:02 ` [PATCH RESEND v2 02/12] selftests/mm: mremap_test: drop munmap() checks from cleanup paths Sarthak Sharma
2026-11-02 10:02 ` [PATCH RESEND v2 03/12] selftests/mm: mremap_test: simplify errno handling Sarthak Sharma
2026-11-02 10:02 ` [PATCH RESEND v2 04/12] selftests/mm: mremap_test: use kselftest helpers Sarthak Sharma
2026-11-02 10:02 ` [PATCH RESEND v2 05/12] selftests/mm: mremap_test: skip test when userfaultfd is unavailable Sarthak Sharma
2026-11-02 10:02 ` [PATCH RESEND v2 06/12] selftests/mm: mremap_test: fail unexpected mremap successes Sarthak Sharma
2026-11-02 10:02 ` [PATCH RESEND v2 07/12] selftests/mm: mremap_test: fail on data corruption Sarthak Sharma
2026-11-02 10:02 ` [PATCH RESEND v2 08/12] selftests/mm: mremap_test: handle cleanup after mmap failures Sarthak Sharma
2026-11-02 10:02 ` [PATCH RESEND v2 09/12] selftests/mm: mremap_test: remove perf tests and timing Sarthak Sharma
2026-11-02 10:02 ` [PATCH RESEND v2 10/12] selftests/mm: mremap_test: replace validation threshold with sampled checks Sarthak Sharma
2026-11-02 10:02 ` [PATCH RESEND v2 11/12] selftests/mm: mremap_test: replace random data with deterministic pattern Sarthak Sharma
2026-11-02 10:02 ` [PATCH RESEND v2 12/12] selftests/mm: mremap_test: strengthen multi VMA validation Sarthak Sharma
2026-11-11 10:13 ` [PATCH RESEND v2 00/12] improve mremap_test Sarthak Sharma
2026-11-16 15:51 ` Lorenzo Stoakes (ARM) [this message]
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=avsmKAf4MRwGdpGI@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@kernel.org \
--cc=jhubbard@nvidia.com \
--cc=kaleshsingh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=sarthak.sharma@arm.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=ts930@dgu.ac.kr \
--cc=vbabka@suse.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