mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Mohamad Alsadhan" <mo@sdhn.cc>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Abdiel Janulgue" <abdiel.janulgue@gmail.com>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Robin Murphy" <robin.murphy@arm.com>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Igor Korotin" <igor.korotin.linux@gmail.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
	"Waiman Long" <longman@redhat.com>,
	"Tamir Duberstein" <tamird@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Mohamad Alsadhan <mo@sdhn.cc>,
	driver-core@lists.linux.dev, rust-for-linux@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] rust: replace `build_assert!` with `const_assert!`
Date: Tue, 26 May 2026 12:33:57 +0800	[thread overview]
Message-ID: <202605261249.YsIyj5Ye-lkp@intel.com> (raw)
In-Reply-To: <20260523122759.30317-1-mo@sdhn.cc>

Hi Mohamad,

kernel test robot noticed the following build errors:

[auto build test ERROR on rust/xarray-next]
[cannot apply to rust/rust-next driver-core/driver-core-testing driver-core/driver-core-next driver-core/driver-core-linus tip/locking/core linus/master v7.1-rc5 next-20260525]
[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/Mohamad-Alsadhan/rust-replace-build_assert-with-const_assert/20260523-202931
base:   https://github.com/Rust-for-Linux/linux xarray-next
patch link:    https://lore.kernel.org/r/20260523122759.30317-1-mo%40sdhn.cc
patch subject: [PATCH RESEND] rust: replace `build_assert!` with `const_assert!`
config: x86_64-randconfig-161-20260526 (https://download.01.org/0day-ci/archive/20260526/202605261249.YsIyj5Ye-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)
smatch: v0.5.0-9185-gbcc58b9c
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260526/202605261249.YsIyj5Ye-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/202605261249.YsIyj5Ye-lkp@intel.com/

All error/warnings (new ones prefixed by >>):

>> error[E0432]: unresolved import `crate::const_assert`
   --> rust/kernel/sync/locked_by.rs:6:5
   |
   6 | use crate::const_assert;
   |     ^^^^^^^------------
   |     |      |
   |     |      help: a similar name exists in the module: `kunit_assert`
   |     no `const_assert` in the root
--
>> error[E0432]: unresolved import `crate::const_assert`
   --> rust/kernel/xarray.rs:8:22
   |
   8 |     alloc, bindings, const_assert,
   |                      ^^^^^^^^^^^^
   |                      |
   |                      no `const_assert` in the root
   |                      help: a similar name exists in the module: `kunit_assert`
--
>> error: cannot find macro `const_assert` in this scope
   --> rust/kernel/list/arc.rs:254:9
   |
   254 |         const_assert!(ID != ID2);
   |         ^^^^^^^^^^^^
--
>> error: cannot find macro `const_assert` in this scope
   --> rust/kernel/i2c.rs:105:9
   |
   105 |         const_assert!(
   |         ^^^^^^^^^^^^
--
>> error: cannot find macro `const_assert` in this scope
   --> rust/kernel/dma.rs:386:9
   |
   386 |         const_assert!(
   |         ^^^^^^^^^^^^
--
>> warning: unused import: `mem::size_of`
   --> rust/kernel/sync/locked_by.rs:7:30
   |
   7 | use core::{cell::UnsafeCell, mem::size_of, ptr};
   |                              ^^^^^^^^^^^^
   |
   = note: `#[warn(unused_imports)]` on by default

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

      reply	other threads:[~2026-05-26  4:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23 12:27 Mohamad Alsadhan
2026-05-26  4:33 ` 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=202605261249.YsIyj5Ye-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=a.hindborg@kernel.org \
    --cc=abdiel.janulgue@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=driver-core@lists.linux.dev \
    --cc=gary@garyguo.net \
    --cc=igor.korotin.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=lossin@kernel.org \
    --cc=mingo@redhat.com \
    --cc=mo@sdhn.cc \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=peterz@infradead.org \
    --cc=robin.murphy@arm.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=will@kernel.org \
    /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®