All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Re: linux-next: build failure after merge of the f2fs tree
Date: Mon, 2 Nov 2020 17:35:56 -0800	[thread overview]
Message-ID: <20201103013556.GA3578719@google.com> (raw)
In-Reply-To: <20201103123112.68f54d17@canb.auug.org.au>

On 11/03, Stephen Rothwell wrote:
> 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.

Thanks, I fixed it in the git directly.

> 
> I have used the version of the f2fs tree from next-20201102 for today.
> 
> -- 
> Cheers,
> Stephen Rothwell



  reply	other threads:[~2020-11-03  1:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03  1:31 linux-next: build failure after merge of the f2fs tree Stephen Rothwell
2020-11-03  1:35 ` Jaegeuk Kim [this message]
  -- 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=20201103013556.GA3578719@google.com \
    --to=jaegeuk@kernel.org \
    --cc=daehojeong@google.com \
    --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 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.