From: kernel test robot <lkp@intel.com>
To: Jason Ekstrand <jason@jlekstrand.net>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: [mlankhorst:xe 161/165] drivers/gpu/drm/xe/xe_ggtt.c:138:6: error: no previous prototype for 'xe_ggtt_invalidate'
Date: Thu, 27 Jan 2022 19:37:26 +0800 [thread overview]
Message-ID: <202201271930.2Cnt0yRu-lkp@intel.com> (raw)
tree: git://people.freedesktop.org/~mlankhorst/linux xe
head: 4bc3039b4403c76a13d58f7ac1f7c07dca6f88d8
commit: 97b49f6fa009a5e8c280503c7f33fedb5d3ddf25 [161/165] xe/ggtt: Invalidate the GGTT TLBs after any updates
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220127/202201271930.2Cnt0yRu-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
git remote add mlankhorst git://people.freedesktop.org/~mlankhorst/linux
git fetch --no-tags mlankhorst xe
git checkout 97b49f6fa009a5e8c280503c7f33fedb5d3ddf25
# save the config file 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 drivers/gpu/drm/xe/xe_ggtt.c:14:
drivers/gpu/drm/xe/xe_mmio.h: In function 'xe_mmio_read64':
drivers/gpu/drm/xe/xe_mmio.h:28:9: error: implicit declaration of function 'readq'; did you mean 'readl'? [-Werror=implicit-function-declaration]
28 | return readq(xe->mmio.regs + reg);
| ^~~~~
| readl
drivers/gpu/drm/xe/xe_ggtt.c: In function 'xe_ggtt_set_pte':
drivers/gpu/drm/xe/xe_ggtt.c:55:2: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
55 | writeq(pte, &ggtt->gsm[addr >> GEN8_PTE_SHIFT]);
| ^~~~~~
| writel
drivers/gpu/drm/xe/xe_ggtt.c: At top level:
>> drivers/gpu/drm/xe/xe_ggtt.c:138:6: error: no previous prototype for 'xe_ggtt_invalidate' [-Werror=missing-prototypes]
138 | void xe_ggtt_invalidate(struct xe_device *xe)
| ^~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/xe_ggtt_invalidate +138 drivers/gpu/drm/xe/xe_ggtt.c
137
> 138 void xe_ggtt_invalidate(struct xe_device *xe)
139 {
140 /* TODO: For GuC, we need to do something different here */
141
142 /* TODO: i915 makes comments about this being uncached and
143 * therefore flushing WC buffers. Is that really true here?
144 */
145 xe_mmio_write32(xe, GFX_FLSH_CNTL_GEN6.reg, GFX_FLSH_CNTL_EN);
146 }
147
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-01-27 11:37 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=202201271930.2Cnt0yRu-lkp@intel.com \
--to=lkp@intel.com \
--cc=jason@jlekstrand.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome