All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Popple <apopple@nvidia.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, zenghui.yu@linux.dev,
	Liam.Howlett@oracle.com,  david@kernel.org, jgg@ziepe.ca,
	leon@kernel.org, linux-kernel@vger.kernel.org,  ljs@kernel.org,
	mhocko@suse.com, rppt@kernel.org, surenb@google.com,
	 vbabka@kernel.org, dri-devel@lists.freedesktop.org,
	balbirs@nvidia.com,  mpenttil@redhat.com
Subject: Re: [PATCH 0/3] Minor hmm_test fixes and cleanups
Date: Wed, 1 Apr 2026 12:20:54 +1100	[thread overview]
Message-ID: <acxxJfyZjDqohVSS@nvdebian.thelocal> (raw)
In-Reply-To: <20260331173313.a471934b6d6b76e64ab9fa2f@linux-foundation.org>

On 2026-04-01 at 11:33 +1100, Andrew Morton <akpm@linux-foundation.org> wrote...
> On Tue, 31 Mar 2026 17:34:42 +1100 Alistair Popple <apopple@nvidia.com> wrote:
> 
> > Just a couple of minor fixups and cleanups for the HMM kernel selftests. These
> > were mostly reported by Zenghui Yu with special thanks to Lorenzo for analysing
> > and pointing out the problems.
> 
> Geeze, if a kernel oops and a ugly WARN are "minor" then I'd hate to
> see your "major".

Heh. Yeah fair. It wouldn't literally set fire to anything but maybe that bar is
too high :)

> I strengthened the [0/N] cover to read "Two bugfixes a cleanup for the
> HMM kernel selftests....".

Thanks.
 
> I also slapped cc:stable on [1/3] and [3/3] and queued everything for
> the upcoming merge window, OK?

Sounds good to me.

> Here I assume that some users of earlier kernels will use that kernel's
> in-kernel selftests.  I don't know how accurate that is, but if they are not
> using them, they don't care!
> 
> [3/3] lacks a Fixes:, but I'm sure the -stable team will figure it out.

Sorry, I shouldn't have been so lazy there. This looks like the correct tag:

Fixes: 6a760f58c792 ("mm/hmm/test: use char dev with struct device to get device node")

Added Mika to 'cc as that's his commit.

> Thanks ;)

      reply	other threads:[~2026-04-01  1:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31  6:34 [PATCH 0/3] Minor hmm_test fixes and cleanups Alistair Popple
2026-03-31  6:34 ` [PATCH 1/3] lib: test_hmm: evict device pages on file close to avoid use-after-free Alistair Popple
2026-03-31  8:47   ` Balbir Singh
2026-04-05  4:35   ` Zenghui Yu
2026-04-05  4:47   ` Zenghui Yu
2026-03-31  6:34 ` [PATCH 2/3] selftests/mm: hmm-tests: don't hardcode THP size to 2MB Alistair Popple
2026-03-31  8:51   ` Balbir Singh
2026-04-01  5:19   ` Matthew Brost
2026-04-01 23:01     ` Matthew Brost
2026-04-02  6:32   ` Sayali Patil
2026-03-31  6:34 ` [PATCH 3/3] lib: test_hmm: Implement a device release method Alistair Popple
2026-03-31  8:53   ` Balbir Singh
2026-04-05  4:47   ` Zenghui Yu
2026-04-01  0:33 ` [PATCH 0/3] Minor hmm_test fixes and cleanups Andrew Morton
2026-04-01  1:20   ` Alistair Popple [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=acxxJfyZjDqohVSS@nvdebian.thelocal \
    --to=apopple@nvidia.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbirs@nvidia.com \
    --cc=david@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mpenttil@redhat.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=zenghui.yu@linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.