From: kernel test robot <lkp@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jgunthorpe:iommufd 1/8] ./usr/include/linux/iommufd.h:7:10: fatal error: uapi/linux/ioctl.h: No such file or directory
Date: Fri, 19 Nov 2021 04:47:49 +0800 [thread overview]
Message-ID: <202111190443.mYKVkkWP-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
tree: https://github.com/jgunthorpe/linux iommufd
head: 4d06b5807e799e0293171d872d8c1a40f3b466c5
commit: 7d982d8a3be5264edbd77796083193af431d8b3c [1/8] iommufd: File descriptor, context, kconfig and makefiles
config: i386-buildonly-randconfig-r002-20211117 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/jgunthorpe/linux/commit/7d982d8a3be5264edbd77796083193af431d8b3c
git remote add jgunthorpe https://github.com/jgunthorpe/linux
git fetch --no-tags jgunthorpe iommufd
git checkout 7d982d8a3be5264edbd77796083193af431d8b3c
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from <command-line>:32:
>> ./usr/include/linux/iommufd.h:7:10: fatal error: uapi/linux/ioctl.h: No such file or directory
7 | #include <uapi/linux/ioctl.h>
| ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38970 bytes --]
reply other threads:[~2021-11-18 20:48 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=202111190443.mYKVkkWP-lkp@intel.com \
--to=lkp@intel.com \
--cc=jgg@nvidia.com \
--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®