From: Andrew Morton <akpm@linux-foundation.org>
To: Ralph Campbell <rcampbell@nvidia.com>
Cc: <linux-mm@kvack.org>, Felix Kuehling <felix.kuehling@amd.com>,
Philip Yang <Philip.Yang@amd.com>,
Alistair Popple <apopple@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [PATCH v3 0/2] mm/hmm: fault non-owner device private entries
Date: Thu, 28 Jul 2022 16:17:27 -0700 [thread overview]
Message-ID: <20220728161727.71a38b3b5e037e934f55c1a8@linux-foundation.org> (raw)
In-Reply-To: <20220727000837.4128709-1-rcampbell@nvidia.com>
On Tue, 26 Jul 2022 17:08:35 -0700 Ralph Campbell <rcampbell@nvidia.com> wrote:
> Andrew's mm tree already has everything except the updated description
> for patch 2.
Thanks, I updated the changelog and the Link: tags in place.
prev parent reply other threads:[~2022-07-28 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 0:08 Ralph Campbell
2022-07-27 0:08 ` [PATCH v3 1/2] " Ralph Campbell
2022-07-27 0:08 ` [PATCH v3 2/2] mm/hmm: add a test for cross device private faults Ralph Campbell
2022-07-28 23:17 ` Andrew Morton [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=20220728161727.71a38b3b5e037e934f55c1a8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Philip.Yang@amd.com \
--cc=apopple@nvidia.com \
--cc=felix.kuehling@amd.com \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=rcampbell@nvidia.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