From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Muchun Song <songmuchun@bytedance.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Oscar Salvador <osalvador@suse.de>
Subject: Re: linux-next: build failures after merge of the mm tree
Date: Wed, 22 Jun 2022 03:04:40 +0100 [thread overview]
Message-ID: <YrJ4uPNlIk1QifAL@casper.infradead.org> (raw)
In-Reply-To: <20220621152845.16c801b4efd747173dc08559@linux-foundation.org>
On Tue, Jun 21, 2022 at 03:28:45PM -0700, Andrew Morton wrote:
> On Mon, 20 Jun 2022 14:51:18 +0100 Matthew Wilcox <willy@infradead.org> wrote:
>
> > On Mon, Jun 20, 2022 at 03:11:31PM +0800, Muchun Song wrote:
> > > Thanks for your report. It is fixed in thread [1].
> > >
> > > https://lore.kernel.org/all/20220619133851.68184-3-songmuchun@bytedance.com/ [1]
> >
> > No, it's a different problem. I suggest dropping/reverting
> >
> > https://lore.kernel.org/linux-mm/20220617175020.717127-20-willy@infradead.org/
>
> Dropping that creates awkwardness. How about just uninlining it?
Sure! We can also make compound_page_dtors static and drop the
declaration in linux/mm.h if we do that. I think there's a pile of
cleanup to be done around freeing pages/folios, partly from accretions
over the decades, and partly from the existence of folios between order
0 and 9. Not to mention Mel's recent addition of high-order PCP caching.
But I don't want to do that for this merge window.
next prev parent reply other threads:[~2022-06-22 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 6:42 linux-next: build failures after merge of the mm tree Stephen Rothwell
2022-06-20 7:11 ` Muchun Song
2022-06-20 13:51 ` Matthew Wilcox
2022-06-21 22:28 ` Andrew Morton
2022-06-22 2:04 ` Matthew Wilcox [this message]
2022-06-21 7:18 ` Stephen Rothwell
2022-06-21 11:14 ` [External] " Muchun Song
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=YrJ4uPNlIk1QifAL@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=osalvador@suse.de \
--cc=sfr@canb.auug.org.au \
--cc=songmuchun@bytedance.com \
/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