mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aboorva Devarajan <aboorvad@linux.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Shuah Khan <shuah@kernel.org>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	Sayali Patil <sayalip@linux.ibm.com>,
	linux-kernel@vger.kernel.org, aboorvad@linux.ibm.com
Subject: Re: [PATCH 0/3] selftests/mm: assorted fixes for hmm-tests
Date: Tue, 19 May 2026 09:33:17 +0530	[thread overview]
Message-ID: <a315968224c2f22da8dea7f7fe16588221378f8e.camel@linux.ibm.com> (raw)
In-Reply-To: <20260512200631.b52b15dd47cdbfb887ab3e3b@linux-foundation.org>

On Tue, 2026-05-12 at 20:06 -0700, Andrew Morton wrote:
> On Mon,  4 May 2026 14:41:05 +0530 Aboorva Devarajan <aboorvad@linux.ibm.com> wrote:
> 
> > This series fixes a few issues in hmm-tests that show up when
> > page-size and huge-page configuration differ from the hardcoded
> > assumptions the tests were written for (PMD/THP sizing, default
> > hugepage size, and related cases).
> > 
> > It also includes a minor fix to exclusive_cow: the test ignored the
> > return value of fork(), so both parent and child ran the same teardown
> > path.
> 
> Thanks.  AI review asked a few reasonable-sounding questions:
> 	https://sashiko.dev/#/patchset/cover.1777870179.git.aboorvad@linux.ibm.com

Hi Andrew,

yes, we will address these and send a v2.

Thanks,
Aboorva

      reply	other threads:[~2026-05-19  4:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04  9:11 Aboorva Devarajan
2026-05-04  9:11 ` [PATCH 1/3] selftests/mm: allow PUD-level entries in compound testcase of hmm tests Aboorva Devarajan
2026-05-04  9:11 ` [PATCH 2/3] selftests/mm: remove hardcoded THP sizing assumptions in " Aboorva Devarajan
2026-05-04  9:11 ` [PATCH 3/3] selftests/mm: fix exclusive_cow test fork() handling Aboorva Devarajan
2026-05-13  3:06 ` [PATCH 0/3] selftests/mm: assorted fixes for hmm-tests Andrew Morton
2026-05-19  4:03   ` Aboorva Devarajan [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=a315968224c2f22da8dea7f7fe16588221378f8e.camel@linux.ibm.com \
    --to=aboorvad@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sayalip@linux.ibm.com \
    --cc=shuah@kernel.org \
    /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
Powered by JetHome