mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 124/165] drivers/gpu/drm/xe/xe_vm.c:160:3: error: implicit declaration of function 'writeq'; did you mean 'writel'?
Date: Thu, 27 Jan 2022 12:04:37 +0800	[thread overview]
Message-ID: <202201271251.UUO143AR-lkp@intel.com> (raw)

tree:   git://people.freedesktop.org/~mlankhorst/linux xe
head:   4bc3039b4403c76a13d58f7ac1f7c07dca6f88d8
commit: 5b618f2bacec0b689def464e9771e604cada24d7 [124/165] xe/vm: Use writeq when is_iomem
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220127/202201271251.UUO143AR-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 5b618f2bacec0b689def464e9771e604cada24d7
        # 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 >>):

   drivers/gpu/drm/xe/xe_vm.c: In function '__xe_pt_write':
>> drivers/gpu/drm/xe/xe_vm.c:160:3: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
     160 |   writeq(data, (uint64_t __iomem *)map_u64);
         |   ^~~~~~
         |   writel
   drivers/gpu/drm/xe/xe_vm.c: At top level:
   drivers/gpu/drm/xe/xe_vm.c:165:15: error: no previous prototype for 'xe_pt_create' [-Werror=missing-prototypes]
     165 | struct xe_pt *xe_pt_create(struct xe_vm *vm, unsigned int level)
         |               ^~~~~~~~~~~~
   cc1: all warnings being treated as errors


vim +160 drivers/gpu/drm/xe/xe_vm.c

   151	
   152	static void __xe_pt_write(struct ttm_bo_kmap_obj *map,
   153				  unsigned int idx, uint64_t data)
   154	{
   155		bool is_iomem;
   156		uint64_t *map_u64;
   157	
   158		map_u64 = ttm_kmap_obj_virtual(map, &is_iomem);
   159		if (is_iomem)
 > 160			writeq(data, (uint64_t __iomem *)map_u64);
   161		else
   162			map_u64[idx] = data;
   163	}
   164	

---
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  4:04 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=202201271251.UUO143AR-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