From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [skeggsb:linux-5.12 6/19] drivers/gpu/drm/nouveau/nvkm/subdev/mc/tu102.c:50:1: sparse: sparse: symbol 'tu102_mc_intr_unarm' was not declared. Should it be
Date: Fri, 29 Jan 2021 16:44:43 +0800 [thread overview]
Message-ID: <202101291627.uhDyQDaa-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]
tree: https://github.com/skeggsb/linux linux-5.12
head: d1f5a3fc85566e9ddce9361ef180f070367e6eab
commit: c3cc12eaf511a8a47ade42f521534255ef8ffd47 [6/19] drm/nouveau/mc/tu102: Fix MMU fault interrupts on Turing
config: i386-randconfig-s001-20210129 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-215-g0fb77bb6-dirty
# https://github.com/skeggsb/linux/commit/c3cc12eaf511a8a47ade42f521534255ef8ffd47
git remote add skeggsb https://github.com/skeggsb/linux
git fetch --no-tags skeggsb linux-5.12
git checkout c3cc12eaf511a8a47ade42f521534255ef8ffd47
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
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/nouveau/nvkm/subdev/mc/tu102.c:50:1: sparse: sparse: symbol 'tu102_mc_intr_unarm' was not declared. Should it be static?
>> drivers/gpu/drm/nouveau/nvkm/subdev/mc/tu102.c:62:1: sparse: sparse: symbol 'tu102_mc_intr_rearm' was not declared. Should it be static?
>> drivers/gpu/drm/nouveau/nvkm/subdev/mc/tu102.c:74:1: sparse: sparse: symbol 'tu102_mc_intr_mask' was not declared. Should it be static?
>> drivers/gpu/drm/nouveau/nvkm/subdev/mc/tu102.c:132:1: sparse: sparse: symbol 'tu102_mc_new_' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 35129 bytes --]
next reply other threads:[~2021-01-29 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 8:44 kernel test robot [this message]
2021-01-29 8:44 ` [RFC PATCH skeggsb] drm/nouveau/mc/tu102: tu102_mc_intr_unarm can be static 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=202101291627.uhDyQDaa-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.