From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Aristeu Rozanski <aris@ruivo.org>, linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH 0/2] mm: gup: cleanup gup_fast call chain
Date: Wed, 29 Jul 2026 08:49:49 +0200 [thread overview]
Message-ID: <8b1cefc4-93b5-4138-9ab5-2dd1cdc7ec78@kernel.org> (raw)
In-Reply-To: <20260219050250.061598056@ruivo.org>
On 2/19/26 06:02, Aristeu Rozanski wrote:
> These two patches implement the refactor in gup_fast call chain David
> Hildenbrand mentioned in
>
> https://lore.kernel.org/all/85e760cf-b994-40db-8d13-221feee55c60@redhat.com/T/#u
>
> Suggested-by: David Hildenbrand <david@kernel.org>
> Link: https://lore.kernel.org/all/85e760cf-b994-40db-8d13-221feee55c60@redhat.com/T/#u
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: David Hildenbrand <david@kernel.org>
> Cc: Jason Gunthorpe <jgg@ziepe.ca>
> Cc: John Hubbard <jhubbard@nvidia.com>
> Cc: Peter Xu <peterx@redhat.com>
> Signed-off-by: Aristeu Rozanski <aris@ruivo.org>
>
Aristeu, I think there were only minor things on the second patch. Can you fix
these up and respin?
We might only queue this after the next merge window, but I don't expect a lot
of conflicts.
--
Cheers,
David
prev parent reply other threads:[~2026-07-29 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 5:02 [PATCH 0/2] mm: gup: cleanup gup_fast call chain Aristeu Rozanski
2026-02-19 5:02 ` [PATCH 1/2] mm: gup: move pmd_protnone() into gup_fast_pmd_leaf() Aristeu Rozanski
2026-02-19 9:21 ` David Hildenbrand (Arm)
2026-02-19 5:02 ` [PATCH 2/2] mm: gup: cleanup the gup_fast_*() call chain Aristeu Rozanski
2026-02-19 9:42 ` David Hildenbrand (Arm)
2026-07-29 6:49 ` David Hildenbrand (Arm) [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=8b1cefc4-93b5-4138-9ab5-2dd1cdc7ec78@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aris@ruivo.org \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.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