From: kernel test robot <lkp@intel.com>
To: Asahi Lina <lina@asahilina.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Janne Grunau <j@jannau.net>
Subject: [asahilinux:asahi 2767/2965] error[E0599]: no function or associated item named `new_with_class` found for struct `Lock` in the current scope
Date: Tue, 24 Sep 2024 16:56:58 +0800 [thread overview]
Message-ID: <202409241627.RpTCQos9-lkp@intel.com> (raw)
tree: https://github.com/AsahiLinux/linux asahi
head: 3416d14cd345b3311b6020714a3bfad7f3dc8b58
commit: 8bf419c887bc5cf6785503b7436ef4328d94702e [2767/2965] rust: sync: Classless Lock::new() and pin_init()
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240924/202409241627.RpTCQos9-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240924/202409241627.RpTCQos9-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/202409241627.RpTCQos9-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0599]: no function or associated item named `new_with_class` found for struct `Lock` in the current scope
--> rust/doctests_kernel_generated.rs:3949:18
|
3949 | d <- new_spinlock!(Inner { a: 20, b: 30 }),
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `Lock<_, SpinLockBackend>`
|
= note: this error originates in the macro `new_spinlock` (in Nightly builds, run with -Z macro-backtrace for more info)
help: there is an associated function `new_with_key` with a similar name
--> rust/kernel/sync/lock/spinlock.rs:14:33
|
14 | $crate::sync::SpinLock::new_with_key(
| ~~~~~~~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-09-24 8: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=202409241627.RpTCQos9-lkp@intel.com \
--to=lkp@intel.com \
--cc=j@jannau.net \
--cc=lina@asahilina.net \
--cc=llvm@lists.linux.dev \
--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