From: kernel test robot <lkp@intel.com>
To: Andrew Davis <afd@ti.com>
Cc: oe-kbuild-all@lists.linux.dev, vigneshr@ti.com, nm@ti.com
Subject: [ti:ti-rt-linux-6.1.y-cicd 251/382] drivers/dma-buf/heaps/carveout-heap.c:363:21: sparse: sparse: symbol 'heap_areas' was not declared. Should it be static?
Date: Mon, 27 Nov 2023 03:10:52 +0800 [thread overview]
Message-ID: <202311270152.fCoMBL0f-lkp@intel.com> (raw)
tree: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-rt-linux-6.1.y-cicd
head: 3a4f51391fe1d39254fed39393815b2879e44d73
commit: 0657a5681046633ab41f6505bcdbc292ee2ce3d4 [251/382] dma-buf: heaps: Add Carveout heap to DMA-BUF Heaps
config: riscv-randconfig-r112-20231126 (https://download.01.org/0day-ci/archive/20231127/202311270152.fCoMBL0f-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce: (https://download.01.org/0day-ci/archive/20231127/202311270152.fCoMBL0f-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/202311270152.fCoMBL0f-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
WARNING: invalid argument to '-march': '_zicbom_zihintpause'
>> drivers/dma-buf/heaps/carveout-heap.c:363:21: sparse: sparse: symbol 'heap_areas' was not declared. Should it be static?
>> drivers/dma-buf/heaps/carveout-heap.c:364:8: sparse: sparse: symbol 'heap_area_count' was not declared. Should it be static?
vim +/heap_areas +363 drivers/dma-buf/heaps/carveout-heap.c
361
362 #define MAX_HEAP_AREAS 7
> 363 struct reserved_mem heap_areas[MAX_HEAP_AREAS];
> 364 size_t heap_area_count;
365
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-26 19:14 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=202311270152.fCoMBL0f-lkp@intel.com \
--to=lkp@intel.com \
--cc=afd@ti.com \
--cc=nm@ti.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vigneshr@ti.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 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.