From: kernel test robot <lkp@intel.com>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Miguel Ojeda <ojeda@kernel.org>, Gary Guo <gary@garyguo.net>
Subject: rust/helpers/mutex.c:11:6: sparse: sparse: symbol 'rust_helper___mutex_init' was not declared. Should it be static?
Date: Wed, 23 Oct 2024 19:48:45 +0800 [thread overview]
Message-ID: <202410231939.DXitQG7R-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c2ee9f594da826bea183ed14f2cc029c719bf4da
commit: d065cc76054d21e48a839a2a19ba99dbc51a4d11 rust: mutex: fix __mutex_init() usage in case of PREEMPT_RT
date: 4 weeks ago
config: um-randconfig-r133-20241023 (https://download.01.org/0day-ci/archive/20241023/202410231939.DXitQG7R-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 5886454669c3c9026f7f27eab13509dd0241f2d6)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241023/202410231939.DXitQG7R-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/202410231939.DXitQG7R-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
>> rust/helpers/mutex.c:11:6: sparse: sparse: symbol 'rust_helper___mutex_init' was not declared. Should it be static?
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/helpers.c: note: in included file:
rust/helpers/spinlock.c:16:6: sparse: sparse: context imbalance in 'rust_helper_spin_lock' - wrong count at exit
rust/helpers/spinlock.c:21:6: sparse: sparse: context imbalance in 'rust_helper_spin_unlock' - unexpected unlock
vim +/rust_helper___mutex_init +11 rust/helpers/mutex.c
10
> 11 void rust_helper___mutex_init(struct mutex *mutex, const char *name,
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-10-23 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 11:48 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-26 13:38 rust/helpers/mutex.c:11:6: sparse: sparse: symbol 'rust_helper___mutex_init' 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=202410231939.DXitQG7R-lkp@intel.com \
--to=lkp@intel.com \
--cc=dirk.behme@de.bosch.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox