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 v3 0/2] mm: gup: cleanup gup_fast call chain
Date: Mon, 7 Sep 2026 14:19:54 +0200 [thread overview]
Message-ID: <fffc191c-37d5-4f00-b73b-91b8d1b45046@kernel.org> (raw)
In-Reply-To: <20260828015542.125576330@ruivo.org>
On 8/28/26 03:55, 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
>
> v2: removed unneeded initializations on the second patch as pointed by David
> v3: fixed gup_fast_pmd_range() nr_pages initialization as pointed by David
>
> 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>
>
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
Andrew, can you queue this? If I manage to set up the new component flow on my
side fairly quickly, I might still pick this my self.
(have to dig through tons of mail first before getting started on that)
--
Cheers,
David
prev parent reply other threads:[~2026-09-07 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 1:55 [PATCH v3 0/2] mm: gup: cleanup gup_fast call chain Aristeu Rozanski
2026-08-28 1:55 ` [PATCH v3 1/2] mm: gup: move pmd_protnone() into gup_fast_pmd_leaf() Aristeu Rozanski
2026-08-28 1:55 ` [PATCH v3 2/2] mm: gup: cleanup the gup_fast_*() call chain Aristeu Rozanski
2026-09-07 12:19 ` 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=fffc191c-37d5-4f00-b73b-91b8d1b45046@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