From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Christian Brauner <christianvanbrauner@gmail.com>
Subject: [brauner-vfs:work.mount.namespace 6/6] ./usr/include/linux/nsfs.h:30:2: error: unknown type name '__u32'
Date: Sat, 20 Jul 2024 00:45:42 +0800 [thread overview]
Message-ID: <202407200025.xjTcP74I-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git work.mount.namespace
head: e35c75b426e13d08020c7b9884f2db4fe15b0cbc
commit: 6972489d7aad005e2a31990058a015e344f6aa4e [6/6] nsfs: iterate through mount namespaces
config: i386-buildonly-randconfig-002-20240719 (https://download.01.org/0day-ci/archive/20240720/202407200025.xjTcP74I-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240720/202407200025.xjTcP74I-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202407200025.xjTcP74I-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from <built-in>:1:
>> ./usr/include/linux/nsfs.h:30:2: error: unknown type name '__u32'
30 | __u32 size;
| ^
./usr/include/linux/nsfs.h:31:2: error: unknown type name '__u32'
31 | __u32 nr_mounts;
| ^
>> ./usr/include/linux/nsfs.h:32:2: error: unknown type name '__u64'
32 | __u64 mnt_ns_id;
| ^
3 errors generated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-19 16:46 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=202407200025.xjTcP74I-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=christianvanbrauner@gmail.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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