From: kernel test robot <lkp@intel.com>
To: Janne Grunau <j@jannau.net>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [asahilinux:bits/250-aop 58/85] warning: associated items `zeroed` and `as_raw` are never used
Date: Mon, 4 Aug 2025 01:44:12 +0200 [thread overview]
Message-ID: <202508040158.UDfPSzBd-lkp@intel.com> (raw)
tree: https://github.com/AsahiLinux/linux bits/250-aop
head: 800be80e4ce2e4872e0d8f2716b2b7c79a0511ef
commit: 589bf67694fd455396952ab520e7219e3b2ae481 [58/85] rust: io: resource: Add owned Resource initialiser
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250804/202508040158.UDfPSzBd-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250804/202508040158.UDfPSzBd-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/202508040158.UDfPSzBd-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> warning: associated items `zeroed` and `as_raw` are never used
--> rust/kernel/io/resource.rs:93:19
|
91 | impl Resource {
| ------------- associated items in this implementation
92 | /// Create a new zeroed [`Resource`]
93 | pub(crate) fn zeroed() -> Self {
| ^^^^^^
...
100 | pub(crate) fn as_raw(&self) -> *mut bindings::resource {
| ^^^^^^
|
= note: `#[warn(dead_code)]` on by default
--
>> warning: used a field initializer for a tuple struct
--> rust/kernel/io/resource.rs:94:9
|
94 | / Resource {
95 | | 0: Opaque::<bindings::resource>::zeroed(),
96 | | }
| |_________^ help: use tuple initialization: `Resource(Opaque::<bindings::resource>::zeroed())`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#init_numbered_fields
= note: `-W clippy::init-numbered-fields` implied by `-W clippy::all`
= help: to override `-W clippy::all` add `#[allow(clippy::init_numbered_fields)]`
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-08-03 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-03 23:44 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-05 1:19 [asahilinux:bits/250-aop 58/85] warning: associated items `zeroed` and `as_raw` are never used 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=202508040158.UDfPSzBd-lkp@intel.com \
--to=lkp@intel.com \
--cc=j@jannau.net \
--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 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.