All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: SeongJae Park <sj@kernel.org>,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH for mm-unstable 0/3] Fix build errors due to folio_test_large() misuse
Date: Wed,  4 May 2022 20:23:23 +0000	[thread overview]
Message-ID: <20220504202323.314656-1-sj@kernel.org> (raw)
In-Reply-To: <YnLdrqzkvzqMPD1U@casper.infradead.org>

On Wed, 4 May 2022 21:10:22 +0100 Matthew Wilcox <willy@infradead.org> wrote:

> On Wed, May 04, 2022 at 08:07:55PM +0000, SeongJae Park wrote:
> > Several commits on 'mm-unstable' replaces 'PageTransHuge()' with
> > 'folio_test_large()' instead of 'folio_test_transhuge()'.  As a result,
> > several build errors occur when 'CONFIG_TRANSPARENT_HUGEPAGE' is unset.
> 
> I sent an entire replacement patch series mere minutes ago which I think
> fixes everything you mention here.  Please check?
> 
> https://lore.kernel.org/linux-mm/20220504182857.4013401-1-willy@infradead.org/T/#t

Thanks for the answer.  Yes, seems the fix has made there :)


Thanks,
SJ


      reply	other threads:[~2022-05-04 20:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 20:07 [PATCH for mm-unstable 0/3] Fix build errors due to folio_test_large() misuse SeongJae Park
2022-05-04 20:07 ` [PATCH for mm-unstable 1/3] mm/vmscan: Use folio_test_transhuge() for THP check SeongJae Park
2022-05-04 20:07 ` [PATCH for mm-unstable 2/3] mm/shmem: " SeongJae Park
2022-05-04 20:07 ` [PATCH for mm-unstable 3/3] " SeongJae Park
2022-05-04 20:10 ` [PATCH for mm-unstable 0/3] Fix build errors due to folio_test_large() misuse Matthew Wilcox
2022-05-04 20:23   ` SeongJae Park [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=20220504202323.314656-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.