From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthew Wilcox <willy@infradead.org>
Cc: William Kucharski <william.kucharski@oracle.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 folio tree
Date: Tue, 4 Jan 2022 18:29:25 +1100 [thread overview]
Message-ID: <20220104182925.0ee8fd17@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
Hi all,
After merging the folio tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from include/linux/socket.h:8,
from include/linux/compat.h:15,
from arch/powerpc/kernel/asm-offsets.c:12:
include/linux/uio.h: In function 'copy_folio_to_iter':
include/linux/uio.h:153:33: error: invalid use of undefined type 'struct folio'
153 | return copy_page_to_iter(&folio->page, offset, bytes, i);
| ^~
Caused by commit
442f739136ee ("iov_iter: Add copy_folio_to_iter()")
struct folio is only forward declared in uio.h. Presumably other builds
include mm_types.h indirectly.
I have used the folio tree from next-20211224 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-01-04 7:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 7:29 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-02 8:04 linux-next: build failure after merge of the folio tree Stephen Rothwell
2022-05-02 10:01 ` Gao Xiang
2022-03-15 10:26 Stephen Rothwell
2022-03-15 14:42 ` Matthew Wilcox
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
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=20220104182925.0ee8fd17@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=william.kucharski@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox