From: kernel test robot <lkp@intel.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Miguel Ojeda <ojeda@kernel.org>,
Danilo Krummrich <dakr@kernel.org>, Gary Guo <gary@garyguo.net>
Subject: drivers/android/binder/rust_binderfs.c:51:6: sparse: sparse: symbol 'rust_binder_devices_param' was not declared. Should it be static?
Date: Wed, 23 Sep 2026 17:44:11 +0800 [thread overview]
Message-ID: <202609231723.xD1MYVan-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: fe2ec83746e501645709761605c2464a44fd2929
commit: 72d33b8bfeacbfdccf2cda4650e8e002def036f8 rust: kasan: add support for Software Tag-Based KASAN
date: 4 months ago
config: arm64-randconfig-r1304-20260923 (https://download.01.org/0day-ci/archive/20260923/202609231723.xD1MYVan-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 5dc57157f12f0ff676e823d9b4d98b45c07e5df2)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260923/202609231723.xD1MYVan-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
| Fixes: 72d33b8bfeac ("rust: kasan: add support for Software Tag-Based KASAN")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609231723.xD1MYVan-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/android/binder/rust_binderfs.c:51:6: sparse: sparse: symbol 'rust_binder_devices_param' was not declared. Should it be static?
vim +/rust_binder_devices_param +51 drivers/android/binder/rust_binderfs.c
eafedbc7c050c44 Alice Ryhl 2025-09-19 50
eafedbc7c050c44 Alice Ryhl 2025-09-19 @51 char *rust_binder_devices_param = CONFIG_ANDROID_BINDER_DEVICES;
eafedbc7c050c44 Alice Ryhl 2025-09-19 52 module_param_named(rust_devices, rust_binder_devices_param, charp, 0444);
eafedbc7c050c44 Alice Ryhl 2025-09-19 53
:::::: The code at line 51 was first introduced by commit
:::::: eafedbc7c050c44744fbdf80bdf3315e860b7513 rust_binder: add Rust Binder driver
:::::: TO: Alice Ryhl <aliceryhl@google.com>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-09-23 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 9:44 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-24 1:31 drivers/android/binder/rust_binderfs.c:51:6: sparse: sparse: symbol 'rust_binder_devices_param' was not declared. Should it be static? kernel test robot
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=202609231723.xD1MYVan-lkp@intel.com \
--to=lkp@intel.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@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 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.