All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the folio tree
Date: Tue, 15 Mar 2022 21:26:10 +1100	[thread overview]
Message-ID: <20220315212610.0f996842@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 666 bytes --]

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.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-03-15 10:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 10:26 Stephen Rothwell [this message]
2022-03-15 14:42 ` linux-next: build failure after merge of the folio tree Matthew Wilcox
  -- 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=20220315212610.0f996842@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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.