linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: david@redhat.com, lorenzo.stoakes@oracle.com,
	Liam.Howlett@oracle.com, vbabka@suse.cz, rppt@kernel.org,
	riel@surriel.com, harry.yoo@oracle.com, linux-mm@kvack.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [Patch v3 0/2] assert rmap behaves as expected
Date: Sun, 17 Aug 2025 20:06:42 -0700	[thread overview]
Message-ID: <20250817200642.c3ca3c89832fd9e0cb5117f4@linux-foundation.org> (raw)
In-Reply-To: <20250818022905.15428-1-richard.weiyang@gmail.com>

On Mon, 18 Aug 2025 02:29:03 +0000 Wei Yang <richard.weiyang@gmail.com> wrote:

> As David suggested, currently we don't have a high level test case to
> verify the behavior of rmap. This patch set introduce the verification
> on rmap by migration.

I'm seeing many rejects here, so please redo against tomorrow's mm-new?

Also, seeing "assert" in the changelogs was a little surprising.  The
term "assert" made me expect to see assertions, such as VM_BUG_ON(). 
Perhaps "test that" would be clearer.



  parent reply	other threads:[~2025-08-18  3:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18  2:29 [Patch v3 0/2] assert rmap behaves as expected Wei Yang
2025-08-18  2:29 ` [Patch v3 1/2] selftests/mm: put general ksm operation into vm_util Wei Yang
2025-08-18  2:29 ` [Patch v3 2/2] selftests/mm: assert rmap behave as expected Wei Yang
2025-08-18  3:06 ` Andrew Morton [this message]
2025-08-18  6:40   ` [Patch v3 0/2] assert rmap behaves " Wei Yang

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=20250817200642.c3ca3c89832fd9e0cb5117f4@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=david@redhat.com \
    --cc=harry.yoo@oracle.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=richard.weiyang@gmail.com \
    --cc=riel@surriel.com \
    --cc=rppt@kernel.org \
    --cc=vbabka@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).