From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Yang Shi <yang@os.amperecomputing.com>,
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 mm-hotfixes tree
Date: Mon, 1 Jul 2024 10:16:41 +1000 [thread overview]
Message-ID: <20240701101641.4fea0ac2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
Hi all,
After merging the mm-hotfixes tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
mm/gup.c: In function 'gup_hugepte':
mm/gup.c:474:25: error: implicit declaration of function 'try_grab_folio_fast'; did you mean 'try_grab_folio'? [-Werror=implicit-function-declaration]
474 | folio = try_grab_folio_fast(page, refs, flags);
| ^~~~~~~~~~~~~~~~~~~
| try_grab_folio
mm/gup.c:474:23: warning: assignment to 'struct folio *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
474 | folio = try_grab_folio_fast(page, refs, flags);
| ^
mm/gup.c: At top level:
mm/gup.c:2747:22: error: conflicting types for 'try_grab_folio_fast'; have 'struct folio *(struct page *, int, unsigned int)'
2747 | static struct folio *try_grab_folio_fast(struct page *page, int refs,
| ^~~~~~~~~~~~~~~~~~~
mm/gup.c:474:25: note: previous implicit declaration of 'try_grab_folio_fast' with type 'int()'
474 | folio = try_grab_folio_fast(page, refs, flags);
| ^~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
Caused by commit
5f408bfe0d13 ("mm: gup: stop abusing try_grab_folio")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-07-01 0:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 0:16 Stephen Rothwell [this message]
2024-07-01 1:01 ` linux-next: build failure after merge of the mm-hotfixes tree Stephen Rothwell
2024-07-01 18:15 ` Yang Shi
2024-07-02 22:44 ` Stephen Rothwell
2024-07-02 23:22 ` Stephen Rothwell
2024-07-03 0:40 ` Yang Shi
-- strict thread matches above, loose matches on Subject: below --
2025-12-07 21:35 Stephen Rothwell
2025-12-08 10:30 ` Maciej Wieczor-Retman
2025-12-09 1:37 ` Andrew Morton
2025-08-21 6:05 Stephen Rothwell
2025-08-21 9:49 ` Harry Yoo
2025-05-28 23:59 Stephen Rothwell
2025-05-29 0:02 ` Andrew Morton
2025-05-29 1:57 ` Stephen Rothwell
2025-05-29 0:03 ` Stephen Rothwell
2023-12-13 22:18 Stephen Rothwell
2023-12-13 23:31 ` Liam R. Howlett
2022-12-12 22:30 Stephen Rothwell
2022-12-13 1:34 ` Kefeng Wang
2022-12-13 2:23 ` Andrew Morton
2022-12-13 2:45 ` Stephen Rothwell
2022-12-13 2:54 ` Kefeng Wang
2022-11-25 1:10 Stephen Rothwell
2022-11-25 5:24 ` Juergen Gross
2022-11-25 5:24 ` Andrew Morton
2022-11-25 5:48 ` Stephen Rothwell
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=20240701101641.4fea0ac2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=yang@os.amperecomputing.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