From: kernel test robot <lkp@intel.com>
To: Ding Xiang Fei <dingxiangfei2009@protonmail.ch>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Miguel Ojeda <ojeda@kernel.org>
Subject: [rust:pr/1130 2/3] error[E0405]: cannot find trait `Unsize` in this scope
Date: Sat, 23 Nov 2024 06:04:58 +0800 [thread overview]
Message-ID: <202411230517.g7Dbe7Ge-lkp@intel.com> (raw)
tree: https://github.com/Rust-for-Linux/linux pr/1130
head: 22607a75f562e7ffa92b8b44ac1574bcb214134d
commit: 36e9396cf5591aa42b19eacba22ee3f7e96bf792 [2/3] gating behind version 1.83.0
config: um-randconfig-001-20241123 (https://download.01.org/0day-ci/archive/20241123/202411230517.g7Dbe7Ge-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 592c0fe55f6d9a811028b5f3507be91458ab2713)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241123/202411230517.g7Dbe7Ge-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/202411230517.g7Dbe7Ge-lkp@intel.com/
Note: the rust/pr/1130 HEAD 22607a75f562e7ffa92b8b44ac1574bcb214134d builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> error[E0405]: cannot find trait `Unsize` in this scope
--> rust/kernel/list/arc.rs:450:26
|
450 | T: ListArcSafe<ID> + Unsize<U> + ?Sized,
| ^^^^^^ not found in this scope
|
help: consider importing this trait
|
7 + use core::marker::Unsize;
|
--
>> error[E0405]: cannot find trait `Unsize` in this scope
--> rust/kernel/list/arc.rs:460:26
|
460 | T: ListArcSafe<ID> + Unsize<U> + ?Sized,
| ^^^^^^ not found in this scope
|
help: consider importing this trait
|
7 + use core::marker::Unsize;
|
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-22 22:05 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=202411230517.g7Dbe7Ge-lkp@intel.com \
--to=lkp@intel.com \
--cc=dingxiangfei2009@protonmail.ch \
--cc=llvm@lists.linux.dev \
--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.