public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Tamir Duberstein" <tamird@gmail.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Andrew Ballance" <andrewjballance@gmail.com>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Trevor Gross" <tmgross@umich.edu>
Cc: oe-kbuild-all@lists.linux.dev, rust-for-linux@vger.kernel.org,
	linux-kernel@vger.kernel.org, Tamir Duberstein <tamird@gmail.com>
Subject: Re: [PATCH 2/2] rust: alloc: add `Vec::dec_len`
Date: Thu, 20 Mar 2025 05:05:08 +0800	[thread overview]
Message-ID: <202503200447.aF1NxDEq-lkp@intel.com> (raw)
In-Reply-To: <20250316-vec-set-len-v1-2-60f98a28723f@gmail.com>

Hi Tamir,

kernel test robot noticed the following build warnings:

[auto build test WARNING on cf25bc61f8aecad9b0c45fe32697e35ea4b13378]

url:    https://github.com/intel-lab-lkp/linux/commits/Tamir-Duberstein/rust-alloc-replace-Vec-set_len-with-inc_len/20250317-103338
base:   cf25bc61f8aecad9b0c45fe32697e35ea4b13378
patch link:    https://lore.kernel.org/r/20250316-vec-set-len-v1-2-60f98a28723f%40gmail.com
patch subject: [PATCH 2/2] rust: alloc: add `Vec::dec_len`
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250320/202503200447.aF1NxDEq-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
rustc: rustc 1.78.0 (9b00956e5 2024-04-29)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250320/202503200447.aF1NxDEq-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/202503200447.aF1NxDEq-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> warning: method `dec_len` is never used
   --> rust/kernel/alloc/kvec.rs:205:15
   |
   161 | / impl<T, A> Vec<T, A>
   162 | | where
   163 | |     A: Allocator,
   | |_________________- method in this implementation
   ...
   205 |       unsafe fn dec_len(&mut self, count: usize) -> &mut [T] {
   |                 ^^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

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

      parent reply	other threads:[~2025-03-19 21:06 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-16 22:31 [PATCH 0/2] rust: alloc: split `Vec::set_len` into `Vec::{inc,dec}_len` Tamir Duberstein
2025-03-16 22:32 ` [PATCH 1/2] rust: alloc: replace `Vec::set_len` with `inc_len` Tamir Duberstein
2025-03-17  9:58   ` Benno Lossin
2025-03-17 10:23     ` Miguel Ojeda
2025-03-17 14:43       ` Benno Lossin
2025-03-17 10:48     ` Alice Ryhl
2025-03-17 11:25       ` Tamir Duberstein
2025-03-17 14:46         ` Benno Lossin
2025-03-17 15:01           ` Tamir Duberstein
2025-03-17 10:50   ` Alice Ryhl
2025-03-17 11:16     ` Danilo Krummrich
2025-03-17 11:25     ` Tamir Duberstein
2025-03-16 22:32 ` [PATCH 2/2] rust: alloc: add `Vec::dec_len` Tamir Duberstein
2025-03-16 22:35   ` Tamir Duberstein
2025-03-16 22:41   ` Danilo Krummrich
2025-03-16 22:47     ` Tamir Duberstein
2025-03-16 23:02       ` Danilo Krummrich
2025-03-16 23:27         ` Tamir Duberstein
2025-03-17 11:22           ` Danilo Krummrich
2025-03-17 11:34             ` Tamir Duberstein
2025-03-17 10:04   ` Benno Lossin
2025-03-17 11:34     ` Tamir Duberstein
2025-03-17 11:47       ` Alice Ryhl
2025-03-17 12:59         ` Alice Ryhl
2025-03-17 13:53           ` Tamir Duberstein
2025-03-18  9:30             ` Alice Ryhl
2025-03-18 14:12               ` Tamir Duberstein
2025-03-18 14:44                 ` Alice Ryhl
2025-03-18 18:28                   ` Tamir Duberstein
2025-03-18 18:46                     ` Danilo Krummrich
2025-03-18 18:53                       ` Tamir Duberstein
2025-03-18 19:26                         ` Danilo Krummrich
2025-03-18 20:05                           ` Tamir Duberstein
2025-03-18 20:13                             ` Tamir Duberstein
2025-03-18 20:15                               ` Danilo Krummrich
2025-03-17 14:42           ` Benno Lossin
2025-03-17 14:44             ` Tamir Duberstein
2025-03-17 16:16               ` Danilo Krummrich
2025-03-17 16:21                 ` Tamir Duberstein
2025-03-17 14:39       ` Benno Lossin
2025-03-17 15:37         ` Tamir Duberstein
2025-03-17 15:57           ` Miguel Ojeda
2025-03-17 17:24           ` Benno Lossin
2025-03-17 17:28             ` Tamir Duberstein
2025-03-19 21:05   ` kernel test robot [this message]

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=202503200447.aF1NxDEq-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=andrewjballance@gmail.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@gmail.com \
    --cc=tmgross@umich.edu \
    /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