From: kernel test robot <lkp@intel.com>
To: Alessio Balsini <balsini@google.com>
Cc: kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org
Subject: [ammarfaizi2-block:google/android/kernel/common/android13-5.10 1034/9999] usr/include/linux/fuse.h:888: found __[us]{8,16,32,64} type without #include <linux/types.h>
Date: Thu, 10 Mar 2022 18:47:44 +0800 [thread overview]
Message-ID: <202203101849.Vpu9XtZ0-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android13-5.10
head: 2d490f129561c7cb45482b0aa866e7b973489e8f
commit: 5e424f85962b0353631642f4da402f2003c218ba [1034/9999] ANDROID: fuse/passthrough: API V2 with __u32 open argument
config: x86_64-randconfig-a004 (https://download.01.org/0day-ci/archive/20220310/202203101849.Vpu9XtZ0-lkp@intel.com/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
reproduce (this is a W=1 build):
# https://github.com/ammarfaizi2/linux-block/commit/5e424f85962b0353631642f4da402f2003c218ba
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android13-5.10
git checkout 5e424f85962b0353631642f4da402f2003c218ba
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> usr/include/linux/fuse.h:888: found __[us]{8,16,32,64} type without #include <linux/types.h>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-10 10:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202203101849.Vpu9XtZ0-lkp@intel.com \
--to=lkp@intel.com \
--cc=balsini@google.com \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®