mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Albab Hasan <albabhasan276@gmail.com>, Miguel Ojeda <ojeda@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	"Albab Hasan" <albabhasan276@gmail.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Robin Murphy" <robin.murphy@arm.com>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: io: convert `PhysAddr` type alias to newtype
Date: Sat, 16 May 2026 00:45:57 +0800	[thread overview]
Message-ID: <202605160005.NTpIKu0B-lkp@intel.com> (raw)
In-Reply-To: <20260504045714.59248-1-albabhasan276@gmail.com>

Hi Albab,

kernel test robot noticed the following build errors:

[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on driver-core/driver-core-next driver-core/driver-core-linus rust/rust-next linus/master v7.1-rc3 next-20260508]
[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/Albab-Hasan/rust-io-convert-PhysAddr-type-alias-to-newtype/20260515-155255
base:   driver-core/driver-core-testing
patch link:    https://lore.kernel.org/r/20260504045714.59248-1-albabhasan276%40gmail.com
patch subject: [PATCH] rust: io: convert `PhysAddr` type alias to newtype
config: loongarch-randconfig-002-20260515 (https://download.01.org/0day-ci/archive/20260516/202605160005.NTpIKu0B-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 5bac06718f502014fade905512f1d26d578a18f3)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260516/202605160005.NTpIKu0B-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/202605160005.NTpIKu0B-lkp@intel.com/

All errors (new ones prefixed by >>):

>> error[E0308]: mismatched types
   --> rust/kernel/io/mem.rs:257:43
   |
   257  |             unsafe { bindings::ioremap_np(res_start, size) }
   |                      -------------------- ^^^^^^^^^ expected `u64`, found `PhysAddr`
   |                      |
   |                      arguments to this function are incorrect
   |
   note: function defined here
   --> rust/bindings/bindings_helpers_generated.rs:1272:12
   |
   1272 |     pub fn ioremap_np(offset: phys_addr_t, size: usize) -> *mut ffi::c_void;
   |            ^^^^^^^^^^
   help: call `Into::into` on this expression to convert `PhysAddr` into `u64`
   |
   257  |             unsafe { bindings::ioremap_np(res_start.into(), size) }
   |                                                    +++++++
--
>> error[E0308]: mismatched types
   --> rust/kernel/io/mem.rs:262:40
   |
   262  |             unsafe { bindings::ioremap(res_start, size) }
   |                      ----------------- ^^^^^^^^^ expected `u64`, found `PhysAddr`
   |                      |
   |                      arguments to this function are incorrect
   |
   note: function defined here
   --> rust/bindings/bindings_helpers_generated.rs:1268:12
   |
   1268 |     pub fn ioremap(offset: phys_addr_t, size: usize) -> *mut ffi::c_void;
   |            ^^^^^^^
   help: call `Into::into` on this expression to convert `PhysAddr` into `u64`
   |
   262  |             unsafe { bindings::ioremap(res_start.into(), size) }
   |                                                 +++++++

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

      parent reply	other threads:[~2026-05-15 16:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04  4:57 Albab Hasan
2026-05-04 22:08 ` Danilo Krummrich
2026-05-05  9:17   ` Albab Hasan
2026-05-15 16:45 ` 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=202605160005.NTpIKu0B-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=a.hindborg@kernel.org \
    --cc=albabhasan276@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=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=lossin@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=rust-for-linux@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®