From: kernel test robot <lkp@intel.com>
To: Zhi Wang <zhiw@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, Dave Airlie <airlied@redhat.com>
Subject: [jfern:nova-core-experiments 225/411] drivers/vfio/pci/nvidia-vgpu/vgpu.c:8:10: fatal error: nvrm/nvtypes.h: No such file or directory
Date: Sat, 8 Mar 2025 12:45:14 +0800 [thread overview]
Message-ID: <202503081234.0IgFNmVI-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jfern/linux.git nova-core-experiments
head: 3b93174b3502247b0c46bd54a7cf5f4105274edb
commit: 0014ea7dabeea93a9bef5878aa309a15fd681edf [225/411] vfio/vgpu_mgr: allocate vGPU FB memory when creating vGPUs
config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20250308/202503081234.0IgFNmVI-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250308/202503081234.0IgFNmVI-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/202503081234.0IgFNmVI-lkp@intel.com/
All errors (new ones prefixed by >>):
cc1: warning: kbuild/src/consumer/drivers/vfio/pci/nvidia-vgpu/include: No such file or directory [-Wmissing-include-dirs]
>> drivers/vfio/pci/nvidia-vgpu/vgpu.c:8:10: fatal error: nvrm/nvtypes.h: No such file or directory
8 | #include <nvrm/nvtypes.h>
| ^~~~~~~~~~~~~~~~
compilation terminated.
vim +8 drivers/vfio/pci/nvidia-vgpu/vgpu.c
7
> 8 #include <nvrm/nvtypes.h>
9 #include <nvrm/common/sdk/nvidia/inc/ctrl/ctrla081.h>
10
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-08 4: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=202503081234.0IgFNmVI-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zhiw@nvidia.com \
/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.