From: SeongJae Park <sj@kernel.org>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
SeongJae Park <sj@kernel.org>
Subject: [PATCH for-mm 0/2] Fix trivial build errors on -mm tree
Date: Wed, 9 Feb 2022 09:41:56 +0000 [thread overview]
Message-ID: <20220209094158.21941-1-sj@kernel.org> (raw)
This patchset fixes a couple of build errors of latest -mm tree.
SeongJae Park (2):
mm/internal: Implement no-op mlock_page_drain() for !CONFIG_MMU
mm/gup: Make migrate_device_page() fails always if
!CONFIG_DEVICE_PRIVATE
mm/gup.c | 9 +++++++++
mm/internal.h | 1 +
2 files changed, 10 insertions(+)
--
2.17.1
next reply other threads:[~2022-02-09 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 9:41 SeongJae Park [this message]
2022-02-09 9:41 ` [PATCH for-mm 1/2] mm/internal: Implement no-op mlock_page_drain() for !CONFIG_MMU SeongJae Park
2022-02-09 15:37 ` Hugh Dickins
2022-02-09 16:19 ` Geert Uytterhoeven
2022-02-10 4:37 ` Hugh Dickins
2022-02-10 4:44 ` [PATCH for-mm 1/2 v2] " Hugh Dickins
2022-02-10 7:58 ` SeongJae Park
2022-02-11 3:58 ` Stephen Rothwell
2022-02-09 9:41 ` [PATCH for-mm 2/2] mm/gup: Make migrate_device_page() fails always if !CONFIG_DEVICE_PRIVATE SeongJae Park
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=20220209094158.21941-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).