From: kernel test robot <lkp@intel.com>
To: Zack Rusin <zackr@vmware.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Martin Krastev <krastevm@vmware.com>
Subject: drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c:123:22: sparse: sparse: symbol 'vmw_pt_sys_placement' was not declared. Should it be static?
Date: Fri, 11 Feb 2022 14:02:44 +0800 [thread overview]
Message-ID: <202202111321.hKklCURO-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f1baf68e1383f6ed93eb9cff2866d46562607a43
commit: f6be23264bbac88d1e2bb39658e1b8a397e3f46d drm/vmwgfx: Introduce a new placement for MOB page tables
date: 2 months ago
config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20220211/202202111321.hKklCURO-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f6be23264bbac88d1e2bb39658e1b8a397e3f46d
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout f6be23264bbac88d1e2bb39658e1b8a397e3f46d
# save the config file to linux build tree
mkdir build_dir
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/gpu/drm/vmwgfx/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c:123:22: sparse: sparse: symbol 'vmw_pt_sys_placement' was not declared. Should it be static?
vim +/vmw_pt_sys_placement +123 drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c
122
> 123 struct ttm_placement vmw_pt_sys_placement = {
124 .num_placement = 1,
125 .placement = &vmw_sys_placement_flags,
126 .num_busy_placement = 1,
127 .busy_placement = &vmw_sys_placement_flags
128 };
129
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2022-02-11 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 6:02 kernel test robot [this message]
2022-03-11 5:18 kernel test robot
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=202202111321.hKklCURO-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=krastevm@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zackr@vmware.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
all inboxes | Powered by JetHome®