public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Janne Grunau <j@jannau.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [asahilinux:bits/250-aop 30/68] warning: associated items `zeroed` and `as_raw` are never used
Date: Tue, 07 Apr 2026 11:55:32 +0800	[thread overview]
Message-ID: <202604041929.qLVyIvqG-lkp@intel.com> (raw)

tree:   https://github.com/AsahiLinux/linux bits/250-aop
head:   f7a3080ba37b989ad2fd83054a4b458af97b635d
commit: 0c779dbcbbeaccf8c0ef734565b512942d3ddeb8 [30/68] rust: io: resource: Add owned Resource initialiser
config: x86_64-buildonly-randconfig-001-20260404 (https://download.01.org/0day-ci/archive/20260404/202604041929.qLVyIvqG-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/20260404/202604041929.qLVyIvqG-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/202604041929.qLVyIvqG-lkp@intel.com/

All warnings (new ones prefixed by >>):

   rust/core.o: warning: objtool: asan.module_ctor+0xd: call without frame pointer save/setup
   rust/core.o: warning: objtool: asan.module_dtor+0xd: call without frame pointer save/setup
   rust/build_error.o: warning: objtool: asan.module_ctor+0xd: call without frame pointer save/setup
   rust/build_error.o: warning: objtool: asan.module_dtor+0xd: call without frame pointer save/setup
>> warning: associated items `zeroed` and `as_raw` are never used
   --> rust/kernel/io/resource.rs:83:19
   |
   81 | impl Resource {
   | ------------- associated items in this implementation
   82 |     /// Create a new zeroed [`Resource`]
   83 |     pub(crate) fn zeroed() -> Self {
   |                   ^^^^^^
   ...
   90 |     pub(crate) fn as_raw(&self) -> *mut bindings::resource {
   |                   ^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-04-07  3:56 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=202604041929.qLVyIvqG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=j@jannau.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