From: kernel test robot <lkp@intel.com>
To: Farzad Farshchi <farzadfr@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Emil Renner Berthing <emil.renner.berthing@canonical.com>,
kernel test robot <lkp@intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [esmil:visionfive 41/45] drivers/nvdla/engine.c:86:9: sparse: sparse: symbol 'bdma_grp_sts' was not declared. Should it be static?
Date: Tue, 2 Aug 2022 17:37:22 +0800 [thread overview]
Message-ID: <202208021719.D3UpRJ0t-lkp@intel.com> (raw)
tree: https://github.com/esmil/linux visionfive
head: d02aa65a24f3cd0d7771349c8812b63482a2bce6
commit: d33164ce8bcd550cd4c8bd902aacfb5f1c971ba6 [41/45] nvdla: add NVDLA driver
config: x86_64-allmodconfig (https://download.01.org/0day-ci/archive/20220802/202208021719.D3UpRJ0t-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/esmil/linux/commit/d33164ce8bcd550cd4c8bd902aacfb5f1c971ba6
git remote add esmil https://github.com/esmil/linux
git fetch --no-tags esmil visionfive
git checkout d33164ce8bcd550cd4c8bd902aacfb5f1c971ba6
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/nvdla/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/nvdla/engine.c:86:9: sparse: sparse: symbol 'bdma_grp_sts' was not declared. Should it be static?
>> drivers/nvdla/engine.c:91:21: sparse: sparse: symbol 'roi_desc' was not declared. Should it be static?
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-02 9:38 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=202208021719.D3UpRJ0t-lkp@intel.com \
--to=lkp@intel.com \
--cc=emil.renner.berthing@canonical.com \
--cc=farzadfr@gmail.com \
--cc=geert@linux-m68k.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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 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®