From: kernel test robot <lkp@intel.com>
To: "Maíra Canal" <mcanal@igalia.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Iago Toral Quiroga <itoral@igalia.com>
Subject: [linux-next:master 3648/6165] drivers/gpu/drm/v3d/v3d_bo.c:178:14: error: call to undeclared function 'vmap'; ISO C99 and later do not support implicit function declarations
Date: Sat, 9 Dec 2023 15:26:39 +0800 [thread overview]
Message-ID: <202312091544.9mAHr8uc-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: bc63de6e6ba0b16652c5fb4b9c9916b9e7ca1f23
commit: 7c13132c4073628b5fe23b5188ac583a2882a6b0 [3648/6165] drm/v3d: Enable BO mapping
config: mips-randconfig-r113-20231209 (https://download.01.org/0day-ci/archive/20231209/202312091544.9mAHr8uc-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce: (https://download.01.org/0day-ci/archive/20231209/202312091544.9mAHr8uc-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/202312091544.9mAHr8uc-lkp@intel.com/
Note: the linux-next/master HEAD bc63de6e6ba0b16652c5fb4b9c9916b9e7ca1f23 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/v3d/v3d_bo.c:25:
drivers/gpu/drm/v3d/v3d_drv.h:319:24: error: use of empty enum
319 | enum v3d_cpu_job_type {};
| ^
>> drivers/gpu/drm/v3d/v3d_bo.c:178:14: error: call to undeclared function 'vmap'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
178 | bo->vaddr = vmap(obj->pages, obj->base.size >> PAGE_SHIFT, VM_MAP,
| ^
drivers/gpu/drm/v3d/v3d_bo.c:178:14: note: did you mean 'bmap'?
include/linux/fs.h:2669:19: note: 'bmap' declared here
2669 | static inline int bmap(struct inode *inode, sector_t *block)
| ^
>> drivers/gpu/drm/v3d/v3d_bo.c:178:61: error: use of undeclared identifier 'VM_MAP'
178 | bo->vaddr = vmap(obj->pages, obj->base.size >> PAGE_SHIFT, VM_MAP,
| ^
>> drivers/gpu/drm/v3d/v3d_bo.c:184:2: error: call to undeclared function 'vunmap'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
184 | vunmap(bo->vaddr);
| ^
drivers/gpu/drm/v3d/v3d_bo.c:184:2: note: did you mean 'iounmap'?
arch/mips/include/asm/io.h:154:6: note: 'iounmap' declared here
154 | void iounmap(const volatile void __iomem *addr);
| ^
4 errors generated.
vim +/vmap +178 drivers/gpu/drm/v3d/v3d_bo.c
173
174 void v3d_get_bo_vaddr(struct v3d_bo *bo)
175 {
176 struct drm_gem_shmem_object *obj = &bo->base;
177
> 178 bo->vaddr = vmap(obj->pages, obj->base.size >> PAGE_SHIFT, VM_MAP,
179 pgprot_writecombine(PAGE_KERNEL));
180 }
181
182 void v3d_put_bo_vaddr(struct v3d_bo *bo)
183 {
> 184 vunmap(bo->vaddr);
185 bo->vaddr = NULL;
186 }
187
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-09 7:30 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=202312091544.9mAHr8uc-lkp@intel.com \
--to=lkp@intel.com \
--cc=itoral@igalia.com \
--cc=linux-mm@kvack.org \
--cc=mcanal@igalia.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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