From: Matthew Wilcox <willy@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the folio tree
Date: Tue, 15 Mar 2022 14:42:01 +0000 [thread overview]
Message-ID: <YjCluUjWNZ9wg4fW@casper.infradead.org> (raw)
In-Reply-To: <20220315212610.0f996842@canb.auug.org.au>
On Tue, Mar 15, 2022 at 09:26:10PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the folio tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> mm/readahead.c: In function 'read_cache_pages_invalidate_page':
> mm/readahead.c:54:17: error: implicit declaration of function 'do_invalidatepage'; did you mean 'd_invalidate'? [-Werror=implicit-function-declaration]
> 54 | do_invalidatepage(page, 0, PAGE_SIZE);
> | ^~~~~~~~~~~~~~~~~
> | d_invalidate
>
> Caused by commit
>
> f1fdabbaae8e ("fs: Turn do_invalidatepage() into folio_invalidate()")
>
> I have used the folio tree from next-20220310 for today.
Sorry about that. Originally, I'd removed that entire function in an
earlier commit, but had to shuffle that commit to after the NFS tree
merges.
There's a new for-next for your merge resolution tomorrow ... not much
I can do about the conflicts, but all your resolutions seemed
reasonable. Fixed a couple of other build bugs noted by the build bots
(ceph & hostfs)
next prev parent reply other threads:[~2022-03-15 14:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 10:26 linux-next: build failure after merge of the folio tree Stephen Rothwell
2022-03-15 14:42 ` Matthew Wilcox [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-02 8:04 Stephen Rothwell
2022-05-02 10:01 ` Gao Xiang
2022-02-28 12:53 Stephen Rothwell
2022-02-17 7:20 Stephen Rothwell
2022-02-15 6:44 Stephen Rothwell
2022-02-07 4:06 Stephen Rothwell
2022-02-09 3:38 ` Stephen Rothwell
2022-02-09 3:47 ` Matthew Wilcox
2022-01-04 7:29 Stephen Rothwell
2021-11-01 6:48 Stephen Rothwell
2021-09-21 4:26 Stephen Rothwell
2021-09-22 4:19 ` Stephen Rothwell
2021-11-01 22:05 ` Stephen Rothwell
2021-11-02 7:02 ` David Howells
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=YjCluUjWNZ9wg4fW@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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