Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v18 16/16] rust: replace `CStr` with `core::ffi::CStr`
Date: Mon, 20 Oct 2025 10:57:09 +0800	[thread overview]
Message-ID: <202510201014.KMYY9XHs-lkp@intel.com> (raw)
In-Reply-To: <20251018180552.3616793-1-aliceryhl@google.com>

Hi Alice,

kernel test robot noticed the following build errors:

[auto build test ERROR on 6f3b6e91f7201e248d83232538db14d30100e9c7]

url:    https://github.com/intel-lab-lkp/linux/commits/Tamir-Duberstein/samples-rust-platform-remove-trailing-commas/20251019-060517
base:   6f3b6e91f7201e248d83232538db14d30100e9c7
patch link:    https://lore.kernel.org/r/20251018180552.3616793-1-aliceryhl%40google.com
patch subject: [PATCH v18 16/16] rust: replace `CStr` with `core::ffi::CStr`
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20251020/202510201014.KMYY9XHs-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/20251020/202510201014.KMYY9XHs-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/202510201014.KMYY9XHs-lkp@intel.com/

All errors (new ones prefixed by >>):

>> error[E0599]: no method named `as_bytes` found for struct `CString` in the current scope
   --> samples/rust/rust_debugfs_scoped.rs:41:38
   |
   41 |         .retain(|device| device.name.as_bytes() != to_remove.as_bytes());
   |                                      ^^^^^^^^
   |
   help: there is a method `to_bytes` with a similar name
   |
   41 -         .retain(|device| device.name.as_bytes() != to_remove.as_bytes());
   41 +         .retain(|device| device.name.to_bytes() != to_remove.as_bytes());
   |
--
>> error[E0599]: no method named `as_bytes` found for reference `&core::ffi::CStr` in the current scope
   --> samples/rust/rust_debugfs_scoped.rs:41:62
   |
   41 |         .retain(|device| device.name.as_bytes() != to_remove.as_bytes());
   |                                                              ^^^^^^^^
   |
   help: there is a method `to_bytes` with a similar name
   |
   41 -         .retain(|device| device.name.as_bytes() != to_remove.as_bytes());
   41 +         .retain(|device| device.name.as_bytes() != to_remove.to_bytes());
   |

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

      reply	other threads:[~2025-10-20  2:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-18 17:45 [PATCH v18 00/16] rust: replace kernel::str::CStr w/ core::ffi::CStr Tamir Duberstein
2025-10-18 17:45 ` [PATCH v18 01/16] samples: rust: platform: remove trailing commas Tamir Duberstein
2025-10-18 17:45 ` [PATCH v18 02/16] rust_binder: remove trailing comma Tamir Duberstein
2025-10-18 17:45 ` [PATCH v18 03/16] rust_binder: use `kernel::fmt` Tamir Duberstein
2025-10-18 17:45 ` [PATCH v18 04/16] rust_binder: use `core::ffi::CStr` method names Tamir Duberstein
2025-10-18 17:45 ` [PATCH v18 05/16] rnull: use `kernel::fmt` Tamir Duberstein
2025-10-18 17:45 ` [PATCH v18 06/16] rust: alloc: " Tamir Duberstein
2025-10-18 17:45 ` [PATCH v18 07/16] rust: debugfs: " Tamir Duberstein
2025-10-18 17:45 ` [PATCH v18 08/16] rust: pci: " Tamir Duberstein
2025-10-18 17:45 ` [PATCH v18 09/16] rust: remove spurious `use core::fmt::Debug` Tamir Duberstein
2025-10-18 17:45 ` [PATCH v18 10/16] rust: opp: use `CStr::as_char_ptr` Tamir Duberstein
2025-10-22  2:26   ` Viresh Kumar
2025-10-18 17:45 ` [PATCH v18 11/16] rust: opp: fix broken rustdoc link Tamir Duberstein
2025-10-22  2:27   ` Viresh Kumar
2025-10-22  4:01     ` Viresh Kumar
2025-10-18 18:03 ` [PATCH v18 12/16] rust: configfs: use `CStr::as_char_ptr` Alice Ryhl
2025-10-20 12:44   ` Andreas Hindborg
2025-10-18 18:03 ` [PATCH v18 13/16] rust: regulator: " Alice Ryhl
2025-10-18 18:03 ` [PATCH v18 14/16] rust: clk: " Alice Ryhl
2025-10-22  2:27   ` Viresh Kumar
2025-10-18 18:03 ` [PATCH v18 15/16] rust: support formatting of foreign types Alice Ryhl
2025-10-18 18:05 ` [PATCH v18 16/16] rust: replace `CStr` with `core::ffi::CStr` Alice Ryhl
2025-10-20  2:57   ` 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=202510201014.KMYY9XHs-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aliceryhl@google.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