From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Hongchen Zhang <zhanghongchen@loongson.cn>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-5.10 23822/30000] drivers/gpu/drm/inspur/inspur_cursor.c:54:32: sparse: sparse: cast removes address space '__iomem' of expression
Date: Thu, 11 Apr 2024 04:08:14 +0800 [thread overview]
Message-ID: <202404110414.lls2ROdf-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-5.10
head: f1776d0ca22cf72bfcdc93dced47d9dde9934d97
commit: b9d65551a3adfa87a7c5d33391187ee60a1b501d [23822/30000] drm: add inspur drm driver support
config: x86_64-randconfig-r122-20240410 (https://download.01.org/0day-ci/archive/20240411/202404110414.lls2ROdf-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240411/202404110414.lls2ROdf-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/202404110414.lls2ROdf-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/inspur/inspur_cursor.c:54:32: sparse: sparse: cast removes address space '__iomem' of expression
--
>> drivers/gpu/drm/inspur/inspur_drm_drv.c:30:13: sparse: sparse: symbol 'inspur_drm_interrupt' was not declared. Should it be static?
vim +/__iomem +54 drivers/gpu/drm/inspur/inspur_cursor.c
49
50 #define HW_FLAG_OFFSET 0x01ffff00
51 #define HW_FLAG_ENABLE 0x1bd40750
52 unsigned char getKVMHWCursorSetting(struct inspur_drm_private *priv)
53 {
> 54 unsigned int value = *(unsigned int *)(priv->fb_map + HW_FLAG_OFFSET);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-10 20: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=202404110414.lls2ROdf-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zhanghongchen@loongson.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.