From: kernel test robot <lkp@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
0day robot <lkp@intel.com>,
Alan Previn <alan.previn.teres.alexis@intel.com>
Subject: drivers/gpu/drm/i915/pxp/intel_pxp_debugfs.c:9:10: fatal error: gt/debugfs_gt.h: No such file or directory
Date: Tue, 28 Sep 2021 09:07:21 +0800 [thread overview]
Message-ID: <202109280942.7MD3Mluk-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]
tree: https://github.com/0day-ci/linux/commits/Alan-Previn/drm-i915-Introduce-Intel-PXP/20210922-150650
head: 7c65d96d4f9e37c2b67ae130fd90efbd3434b1dd
commit: af63fce3f009071f93c1483f9e31ced4bd805730 drm/i915/pxp: add pxp debugfs
date: 6 days ago
config: i386-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/af63fce3f009071f93c1483f9e31ced4bd805730
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Alan-Previn/drm-i915-Introduce-Intel-PXP/20210922-150650
git checkout af63fce3f009071f93c1483f9e31ced4bd805730
# 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 >>):
>> drivers/gpu/drm/i915/pxp/intel_pxp_debugfs.c:9:10: fatal error: gt/debugfs_gt.h: No such file or directory
9 | #include "gt/debugfs_gt.h"
| ^~~~~~~~~~~~~~~~~
compilation terminated.
vim +9 drivers/gpu/drm/i915/pxp/intel_pxp_debugfs.c
8
> 9 #include "gt/debugfs_gt.h"
10 #include "pxp/intel_pxp.h"
11 #include "pxp/intel_pxp_irq.h"
12 #include "i915_drv.h"
13
---
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: 66061 bytes --]
reply other threads:[~2021-09-28 1:08 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=202109280942.7MD3Mluk-lkp@intel.com \
--to=lkp@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=daniele.ceraolospurio@intel.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