From: kernel test robot <lkp@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, intel-xe@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [drm-xe:drm-xe-next 2/3] drivers/gpu/drm/xe/xe_ggtt.c:78:9: error: implicit declaration of function 'writeq'; did you mean 'writel'?
Date: Sat, 24 Feb 2024 19:49:03 +0800 [thread overview]
Message-ID: <202402241903.R5J8hKVI-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
head: a9e483dda3efa5b9aae5d9eef94d2c3a878d9bea
commit: 3121fed0c51beb8ea7b18ab2ceff1ac9e358ac53 [2/3] drm/xe: Cleanup some layering in GGTT
config: microblaze-allmodconfig (https://download.01.org/0day-ci/archive/20240224/202402241903.R5J8hKVI-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240224/202402241903.R5J8hKVI-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/202402241903.R5J8hKVI-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/xe/xe_ggtt.c: In function 'xe_ggtt_set_pte':
>> drivers/gpu/drm/xe/xe_ggtt.c:78:9: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
78 | writeq(pte, &ggtt->gsm[addr >> XE_PTE_SHIFT]);
| ^~~~~~
| writel
cc1: some warnings being treated as errors
vim +78 drivers/gpu/drm/xe/xe_ggtt.c
dd08ebf6c3525a Matthew Brost 2023-03-30 72
dd08ebf6c3525a Matthew Brost 2023-03-30 73 void xe_ggtt_set_pte(struct xe_ggtt *ggtt, u64 addr, u64 pte)
dd08ebf6c3525a Matthew Brost 2023-03-30 74 {
c73acc1eeba5e3 Francois Dugast 2023-09-12 75 xe_tile_assert(ggtt->tile, !(addr & XE_PTE_MASK));
c73acc1eeba5e3 Francois Dugast 2023-09-12 76 xe_tile_assert(ggtt->tile, addr < ggtt->size);
dd08ebf6c3525a Matthew Brost 2023-03-30 77
58e19acf0cdf3f Lucas De Marchi 2023-04-12 @78 writeq(pte, &ggtt->gsm[addr >> XE_PTE_SHIFT]);
dd08ebf6c3525a Matthew Brost 2023-03-30 79 }
dd08ebf6c3525a Matthew Brost 2023-03-30 80
:::::: The code at line 78 was first introduced by commit
:::::: 58e19acf0cdf3f18c1c868165f45d3ea626b9c3f drm/xe: Cleanup page-related defines
:::::: TO: Lucas De Marchi <lucas.demarchi@intel.com>
:::::: CC: Rodrigo Vivi <rodrigo.vivi@intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-24 11:49 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=202402241903.R5J8hKVI-lkp@intel.com \
--to=lkp@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rodrigo.vivi@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