public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 <kernel@esmil.dk>,
	kernel test robot <lkp@intel.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [esmil:visionfive 38/42] drivers/nvdla/engine.c:86:9: sparse: sparse: symbol 'bdma_grp_sts' was not declared. Should it be static?
Date: Fri, 16 Sep 2022 21:09:18 +0800	[thread overview]
Message-ID: <202209162028.i6FOASKl-lkp@intel.com> (raw)

tree:   https://github.com/esmil/linux visionfive
head:   6ddc6d1b0947a4433b734808f228d1ff253dc46a
commit: 42c828888fd79d43a7eda2ed2d92aad848b98591 [38/42] nvdla: add NVDLA driver
config: arm64-randconfig-s041-20220916 (https://download.01.org/0day-ci/archive/20220916/202209162028.i6FOASKl-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.1.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.4-39-gce1a6720-dirty
        # https://github.com/esmil/linux/commit/42c828888fd79d43a7eda2ed2d92aad848b98591
        git remote add esmil https://github.com/esmil/linux
        git fetch --no-tags esmil visionfive
        git checkout 42c828888fd79d43a7eda2ed2d92aad848b98591
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=arm64 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?

vim +/bdma_grp_sts +86 drivers/nvdla/engine.c

    85	
  > 86	uint8_t bdma_grp_sts[2] = {
    87		FIELD_ENUM(BDMA_STATUS_0, IDLE, YES),
    88		FIELD_ENUM(BDMA_STATUS_0, IDLE, YES)
    89	};
    90	
  > 91	struct dla_roi_desc roi_desc;
    92	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-09-16 13:10 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=202209162028.i6FOASKl-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=farzadfr@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=kbuild-all@lists.01.org \
    --cc=kernel@esmil.dk \
    --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