From: kernel test robot <lkp@intel.com>
To: Manos Pitsidianakis <manos@pitsidianak.is>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
0day robot <lkp@intel.com>
Subject: warning: variable does not need to be mutable
Date: Sat, 16 May 2026 17:51:08 +0200 [thread overview]
Message-ID: <202605161734.3uEaaFFK-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Manos-Pitsidianakis/rust-bindings-generate-virtio-bindings/20260513-065912
head: dcbb217532e1f25cb932bf8b1019d1085373a6df
commit: dcbb217532e1f25cb932bf8b1019d1085373a6df samples/rust: Add sample virtio-rtc driver [WIP]
date: 4 days ago
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260516/202605161734.3uEaaFFK-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/20260516/202605161734.3uEaaFFK-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/202605161734.3uEaaFFK-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> warning: variable does not need to be mutable
--> samples/rust/rust_virtio_rtc.rs:338:17
|
338 | let mut is_exposed = false;
| ----^^^^^^^^^^
| |
| help: remove this `mut`
|
= note: `#[warn(unused_mut)]` on by default
--
>> warning: variants `Tai` and `Monotonic` are never constructed
--> samples/rust/rust_virtio_rtc.rs:113:5
|
109 | enum ClockType {
| --------- variants in this enum
...
113 | Tai = 1,
| ^^^
114 | #[doc(alias = "VIRTIO_RTC_CLOCK_MONOTONIC")]
115 | Monotonic = 2,
| ^^^^^^^^^
|
= note: `#[warn(dead_code)]` on by default
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-16 15:51 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=202605161734.3uEaaFFK-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=manos@pitsidianak.is \
--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.