From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Daeho Jeong <daehojeong@google.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 f2fs tree
Date: Tue, 3 Nov 2020 12:31:12 +1100 [thread overview]
Message-ID: <20201103123112.68f54d17@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
Hi all,
After merging the f2fs tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from <command-line>:32:
./usr/include/linux/f2fs.h:92:2: error: unknown type name 'u8'
92 | u8 algorithm;
| ^~
./usr/include/linux/f2fs.h:93:2: error: unknown type name 'u8'
93 | u8 log_cluster_size;
| ^~
Caused by commit
63d18d4913e5 ("f2fs: add F2FS_IOC_GET_COMPRESS_OPTION ioctl")
You should only use the "__" versions of types in uapi headers.
I have used the version of the f2fs tree from next-20201102 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-11-03 1:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 1:31 Stephen Rothwell [this message]
2020-11-03 1:35 ` linux-next: build failure after merge of the f2fs tree Jaegeuk Kim
-- strict thread matches above, loose matches on Subject: below --
2021-07-23 1:11 Stephen Rothwell
2021-08-27 0:28 ` Stephen Rothwell
2021-06-23 0:49 Stephen Rothwell
2021-07-11 3:08 ` Stephen Rothwell
2019-05-02 0:53 Stephen Rothwell
2019-05-02 3:42 ` Jaegeuk Kim
2018-01-17 23:04 Stephen Rothwell
2014-11-05 0:58 Stephen Rothwell
2013-08-27 1:41 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=20201103123112.68f54d17@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).