From: David Hildenbrand <david@redhat.com>
To: Josef Bacik <josef@toxicpanda.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
kernel-team@fb.com
Subject: Re: [PATCH 2/2] mm: remove foll_flags in __get_user_pages
Date: Fri, 19 Jul 2024 15:24:16 +0200 [thread overview]
Message-ID: <35742ece-e823-40c0-8443-197e197ec155@redhat.com> (raw)
In-Reply-To: <1e79b84bd30287cc9847f2aeb002374e6e60a10f.1721337845.git.josef@toxicpanda.com>
On 18.07.24 23:26, Josef Bacik wrote:
> Now that we're not passing around a pointer to the flags, there's no
> reason to have an extra variable for the gup_flags, simply pass the
> gup_flags directly everywhere.
>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
> ---
Acked-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-07-19 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1721337845.git.josef@toxicpanda.com>
2024-07-18 21:26 ` [PATCH 1/2] mm: cleanup flags usage in faultin_page Josef Bacik
2024-07-19 13:19 ` David Hildenbrand
2024-07-18 21:26 ` [PATCH 2/2] mm: remove foll_flags in __get_user_pages Josef Bacik
2024-07-19 13:24 ` David Hildenbrand [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=35742ece-e823-40c0-8443-197e197ec155@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-mm@kvack.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