From: kernel test robot <lkp@intel.com>
To: Joel Fernandes <joelagnelf@nvidia.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Eliot Courtney <ecourtney@nvidia.com>,
Alexandre Courbot <acourbot@nvidia.com>
Subject: [linux-next:master 4098/19853] warning: associated function `from_raw` is never used
Date: Sat, 24 Oct 2026 11:10:01 +0800 [thread overview]
Message-ID: <202610241133.L9VWoFcD-lkp@intel.com> (raw)
Hi Joel,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: bd1ecbb61afefc6a8b876ccbc31e9228b44e9eab
commit: 3f1e12fce16f6e88fbaab3404df33f65c8f4df87 [4098/19853] rust: pci: add resource_flags accessor
config: x86_64-buildonly-randconfig-1005-20261024 (https://download.01.org/0day-ci/archive/20261024/202610241133.L9VWoFcD-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261024/202610241133.L9VWoFcD-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/202610241133.L9VWoFcD-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> warning: associated function `from_raw` is never used
--> rust/kernel/io/resource.rs:240:25
|
216 | impl Flags {
| ---------- associated function in this implementation
...
240 | pub(crate) const fn from_raw(value: c_ulong) -> Self {
| ^^^^^^^^
|
= note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
--
llvm-nm: error: rust/helpers/helpers.o: No such file or directory
>> warning: associated function `from_raw` is never used
--> rust/kernel/io/resource.rs:240:25
|
216 | impl Flags {
| ---------- associated function in this implementation
...
240 | pub(crate) const fn from_raw(value: c_ulong) -> Self {
| ^^^^^^^^
|
= note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-24 3:10 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=202610241133.L9VWoFcD-lkp@intel.com \
--to=lkp@intel.com \
--cc=acourbot@nvidia.com \
--cc=ecourtney@nvidia.com \
--cc=joelagnelf@nvidia.com \
--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