From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18-kminext 1/1] drivers/vfio/vfio_main.c:65:6: sparse: sparse: symbol 'allow_non_coherent' was not declared. Should it be static?
Date: Fri, 17 Jul 2026 19:57:10 +0800 [thread overview]
Message-ID: <202607171935.pzIPaD2n-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android17-6.18-kminext
head: 9a6f48bb2f89b94bc6857fece1131c450c0d5bee
commit: 88e59f90e918a5d074d07e6f6c5af7a58317a1d4 [1/1] ANDROID: drivers/vfio: Allow non-coherent device for pKVM
config: i386-randconfig-r133-20260717 (https://download.01.org/0day-ci/archive/20260717/202607171935.pzIPaD2n-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260717/202607171935.pzIPaD2n-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/202607171935.pzIPaD2n-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/vfio/vfio_main.c:65:6: sparse: sparse: symbol 'allow_non_coherent' was not declared. Should it be static?
vim +/allow_non_coherent +65 drivers/vfio/vfio_main.c
64
> 65 bool allow_non_coherent __read_mostly;
66 module_param(allow_non_coherent, bool, 0444);
67 MODULE_PARM_DESC(allow_non_coherent, "Allow binding of non-coherent devices, not supported with type1 IOMMU. (default: false)");
68
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-17 11:57 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=202607171935.pzIPaD2n-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox