From: kernel test robot <lkp@intel.com>
To: "Christian Göttsche" <cgzones@googlemail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Christian Brauner <christianvanbrauner@gmail.com>,
Christian Brauner <brauner@kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: [brauner-vfs:vfs.xattr 2/5] ./usr/include/linux/xattr.h:25:2: error: unknown type name '__aligned_u64'
Date: Wed, 1 May 2024 21:55:44 +0800 [thread overview]
Message-ID: <202405012137.vO3QRlq7-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.xattr
head: 0703b9aad555387113b9112cdc84469d12fda266
commit: 71491cbe0205be53be1a044594698eb21c1c15f4 [2/5] fs/xattr: add *at family syscalls
config: i386-buildonly-randconfig-006-20240501 (https://download.01.org/0day-ci/archive/20240501/202405012137.vO3QRlq7-lkp@intel.com/config)
compiler: clang version 18.1.4 (https://github.com/llvm/llvm-project e6c3289804a67ea0bb6a86fadbe454dd93b8d855)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240501/202405012137.vO3QRlq7-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/202405012137.vO3QRlq7-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from <built-in>:1:
>> ./usr/include/linux/xattr.h:25:2: error: unknown type name '__aligned_u64'
25 | __aligned_u64 value;
| ^
>> ./usr/include/linux/xattr.h:26:2: error: unknown type name '__u32'
26 | __u32 size;
| ^
./usr/include/linux/xattr.h:27:2: error: unknown type name '__u32'
27 | __u32 flags;
| ^
3 errors generated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-01 13:56 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=202405012137.vO3QRlq7-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=cgzones@googlemail.com \
--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