From: Christoph Hellwig <hch@infradead.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Peter Xu <peterx@redhat.com>, Jason Gunthorpe <jgg@ziepe.ca>,
David Hildenbrand <david@redhat.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [PATCH v4 5/5] mm/gup: remove unused get_user_pages_locked()
Date: Thu, 3 Feb 2022 23:27:25 -0800 [thread overview]
Message-ID: <YfzVXZVUmmwLNqlm@infradead.org> (raw)
In-Reply-To: <20220204020010.68930-6-jhubbard@nvidia.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2022-02-04 7:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 2:00 [PATCH v4 0/5] mm/gup: some cleanups John Hubbard
2022-02-04 2:00 ` [PATCH v4 1/5] mm: Fix invalid page pointer returned with FOLL_PIN gups John Hubbard
2022-02-04 7:25 ` Christoph Hellwig
2022-02-07 5:19 ` John Hubbard
2022-02-04 11:42 ` Jan Kara
2022-02-04 2:00 ` [PATCH v4 2/5] mm/gup: follow_pfn_pte(): -EEXIST cleanup John Hubbard
2022-02-04 7:25 ` Christoph Hellwig
2022-02-04 11:41 ` Jan Kara
2022-02-04 2:00 ` [PATCH v4 3/5] mm/gup: remove unused pin_user_pages_locked() John Hubbard
2022-02-04 2:00 ` [PATCH v4 4/5] mm: change lookup_node() to use get_user_pages_fast() John Hubbard
2022-02-04 7:27 ` Christoph Hellwig
2022-02-04 2:00 ` [PATCH v4 5/5] mm/gup: remove unused get_user_pages_locked() John Hubbard
2022-02-04 7:27 ` Christoph Hellwig [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=YfzVXZVUmmwLNqlm@infradead.org \
--to=hch@infradead.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=jack@suse.cz \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lukas.bulwahn@gmail.com \
--cc=peterx@redhat.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).