linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: peterx@redhat.com
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	SeongJae Park <sj@kernel.org>,
	peterx@redhat.com
Subject: [PATCH 0/2] mm: small fixup series for mm-unstable
Date: Fri, 22 Mar 2024 23:33:08 -0400	[thread overview]
Message-ID: <20240323033310.971447-1-peterx@redhat.com> (raw)

From: Peter Xu <peterx@redhat.com>

Andrew,

This is the small series that should fixes the two reported issues on
mm-unstable for this series:

https://lore.kernel.org/r/20240321220802.679544-1-peterx@redhat.com

This is build tested on (1) x86_64, allnoconfig+allmodconfig, (2) m68k,
allnoconfig+allmodconfig.

Please consider dropping below quickfix:

  mm-gup-handle-hugepd-for-follow_page-fix

Then apply these two fixups.

Sorry this "small" fixup series is not that small.  Said that, I tested
apply and the fixup should auto-squash all fine on current mm-unstable with
a rebase.  If not, feel free to let me know if you want me to resend the
whole series with a base commit, or whatever easy for you.

Thanks,

Peter Xu (2):
  fixup! mm: make HPAGE_PXD_* macros even if !THP
  fixup! mm/gup: handle hugepd for follow_page()

 include/linux/huge_mm.h |  16 ++-
 mm/gup.c                | 287 ++++++++++++++++++++--------------------
 2 files changed, 154 insertions(+), 149 deletions(-)

-- 
2.44.0



             reply	other threads:[~2024-03-23  3:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23  3:33 peterx [this message]
2024-03-23  3:33 ` [PATCH 1/2] fixup! mm: make HPAGE_PXD_* macros even if !THP peterx
2024-03-23  3:33 ` [PATCH 2/2] fixup! mm/gup: handle hugepd for follow_page() peterx
2024-03-23 17:51 ` [PATCH 0/2] mm: small fixup series for mm-unstable 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=20240323033310.971447-1-peterx@redhat.com \
    --to=peterx@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sj@kernel.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).