From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:mirror-poly-aosp-pixel-lajolla-staging 1/1] drivers/dma-buf/dma-buf.c:42:1: sparse: sparse: symbol 'dmabuf_accounting_key' was not declared. Should it be static?
Date: Mon, 30 Mar 2026 13:17:24 +0800 [thread overview]
Message-ID: <202603301328.7CUbS0Ol-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common mirror-poly-aosp-pixel-lajolla-staging
head: b050398b89b00b305b45dd70b8ab91470c42f155
commit: fa99e30c77d66fe736ceda786695b70dac853899 [1/1] ANDROID: add command line parameter for dmabuf accounting
config: arm-randconfig-r132-20260330 (https://download.01.org/0day-ci/archive/20260330/202603301328.7CUbS0Ol-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 2cd67b8b69f78e3f95918204320c3075a74ba16c)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260330/202603301328.7CUbS0Ol-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/202603301328.7CUbS0Ol-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/dma-buf/dma-buf.c:42:1: sparse: sparse: symbol 'dmabuf_accounting_key' was not declared. Should it be static?
vim +/dmabuf_accounting_key +42 drivers/dma-buf/dma-buf.c
41
> 42 DEFINE_STATIC_KEY_TRUE(dmabuf_accounting_key);
43
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-30 5:17 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=202603301328.7CUbS0Ol-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.