From: kernel test robot <lkp@intel.com>
To: "Christian S. Lima" <christiansantoslima21@gmail.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>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
~lkcamp/patches@lists.sr.ht, richard120310@gmail.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v8] rust: transmute: Add methods for FromBytes trait
Date: Wed, 25 Jun 2025 10:39:29 +0800 [thread overview]
Message-ID: <202506251052.onsnGcvR-lkp@intel.com> (raw)
In-Reply-To: <20250624042802.105623-1-christiansantoslima21@gmail.com>
Hi Christian,
kernel test robot noticed the following build errors:
[auto build test ERROR on rust/rust-next]
[also build test ERROR on linus/master v6.16-rc3 next-20250624]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Christian-S-Lima/rust-transmute-Add-methods-for-FromBytes-trait/20250624-123012
base: https://github.com/Rust-for-Linux/linux rust-next
patch link: https://lore.kernel.org/r/20250624042802.105623-1-christiansantoslima21%40gmail.com
patch subject: [PATCH v8] rust: transmute: Add methods for FromBytes trait
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250625/202506251052.onsnGcvR-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/20250625/202506251052.onsnGcvR-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/202506251052.onsnGcvR-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0658]: use of unstable library feature 'pointer_is_aligned'
--> rust/kernel/transmute.rs:74:68
|
74 | if bytes.len() == ::core::mem::size_of::<T>() && slice_ptr.is_aligned() {
| ^^^^^^^^^^
|
= note: see issue #96284 <https://github.com/rust-lang/rust/issues/96284> for more information
= help: add `#![feature(pointer_is_aligned)]` to the crate attributes to enable
= note: this compiler was built on 2024-04-29; consider upgrading it if it is out of date
--
>> error[E0658]: use of unstable library feature 'pointer_is_aligned'
--> rust/kernel/transmute.rs:87:68
|
87 | if bytes.len() == ::core::mem::size_of::<T>() && slice_ptr.is_aligned() {
| ^^^^^^^^^^
|
= note: see issue #96284 <https://github.com/rust-lang/rust/issues/96284> for more information
= help: add `#![feature(pointer_is_aligned)]` to the crate attributes to enable
= note: this compiler was built on 2024-04-29; consider upgrading it if it is out of date
--
>> error[E0658]: use of unstable library feature 'pointer_is_aligned'
--> rust/kernel/transmute.rs:101:72
|
101 | if bytes.len() % ::core::mem::size_of::<T>() == 0 && slice_ptr.is_aligned() {
| ^^^^^^^^^^
|
= note: see issue #96284 <https://github.com/rust-lang/rust/issues/96284> for more information
= help: add `#![feature(pointer_is_aligned)]` to the crate attributes to enable
= note: this compiler was built on 2024-04-29; consider upgrading it if it is out of date
--
>> error[E0658]: use of unstable library feature 'pointer_is_aligned'
--> rust/kernel/transmute.rs:114:72
|
114 | if bytes.len() % ::core::mem::size_of::<T>() == 0 && slice_ptr.is_aligned() {
| ^^^^^^^^^^
|
= note: see issue #96284 <https://github.com/rust-lang/rust/issues/96284> for more information
= help: add `#![feature(pointer_is_aligned)]` to the crate attributes to enable
= note: this compiler was built on 2024-04-29; consider upgrading it if it is out of date
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-25 2:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 4:28 Christian S. Lima
2025-06-25 2:39 ` kernel test robot [this message]
2025-07-07 5:14 ` Alexandre Courbot
2025-07-14 22:16 ` Christian
2025-07-22 14:06 ` Alexandre Courbot
2025-07-25 18:37 ` Christian
2025-07-26 2:57 ` Alexandre Courbot
2025-07-27 1:37 ` Kane York
2025-07-28 19:39 ` Christian
2025-07-28 21:21 ` K. York
2025-08-01 12:26 ` Alexandre Courbot
2025-08-01 15:35 ` Miguel Ojeda
2025-08-01 17:47 ` Christian
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=202506251052.onsnGcvR-lkp@intel.com \
--to=lkp@intel.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=christiansantoslima21@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=richard120310@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=~lkcamp/patches@lists.sr.ht \
/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
all inboxes | Powered by JetHome®