From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: intel-xe@lists.freedesktop.org,
Alistair Popple <apopple@nvidia.com>,
Ralph Campbell <rcampbell@nvidia.com>,
Christoph Hellwig <hch@lst.de>,
Jason Gunthorpe <jgg@mellanox.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Leon Romanovsky <leon@kernel.org>,
Matthew Brost <matthew.brost@intel.com>,
John Hubbard <jhubbard@nvidia.com>,
linux-mm@kvack.org, dri-devel@lists.freedesktop.org,
stable@vger.kernel.org
Subject: Re: [PATCH v4] mm: Fix a hmm_range_fault() livelock / starvation problem
Date: Thu, 12 Feb 2026 09:52:43 +0100 [thread overview]
Message-ID: <cce7d407e4749023271d39653cb7cef78e1a60a3.camel@linux.intel.com> (raw)
In-Reply-To: <20260209173446.b76547c4028132f71de1b8eb@linux-foundation.org>
On Mon, 2026-02-09 at 17:34 -0800, Andrew Morton wrote:
> On Mon, 09 Feb 2026 15:47:38 +0100 Thomas Hellström
> <thomas.hellstrom@linux.intel.com> wrote:
>
> > @Alistair, any chance of an R-B for the below version?
>
> Yes please.
>
> > @Andrew, will this go through the -mm tree or alternaltively an ack
> > for
> > merging through drm-xe-fixes?
>
> Either works. I'll grab a copy. It you want to take this via drm
> then
> I'll drop the mm.git copy once the drm tree's version appears in
> linux-next.
>
> Acked-by: Andrew Morton <akpm@linux-foundation.org>
>
> >
The drm tree's version now appears in linux-next as
a69d1ab971a624c6f112cea61536569d579c3215
Thanks,
Thomas
next prev parent reply other threads:[~2026-02-12 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 11:10 Thomas Hellström
2026-02-05 11:20 ` Balbir Singh
2026-02-05 12:41 ` Thomas Hellström
2026-02-10 2:47 ` Balbir Singh
2026-02-09 14:47 ` Thomas Hellström
2026-02-10 1:34 ` Andrew Morton
2026-02-12 8:52 ` Thomas Hellström [this message]
2026-02-10 2:22 ` Alistair Popple
2026-02-10 2:56 ` Balbir Singh
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=cce7d407e4749023271d39653cb7cef78e1a60a3.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=intel-xe@lists.freedesktop.org \
--cc=jgg@mellanox.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=rcampbell@nvidia.com \
--cc=stable@vger.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