From: kernel test robot <lkp@intel.com>
To: Asahi Lina <lina@asahilina.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Janne Grunau <j@jannau.net>
Subject: [asahilinux:bits/250-aop 34/68] error[E0061]: this function takes 1 argument but 2 arguments were supplied
Date: Tue, 07 Apr 2026 11:58:59 +0800 [thread overview]
Message-ID: <202604051411.VGXONaOa-lkp@intel.com> (raw)
tree: https://github.com/AsahiLinux/linux bits/250-aop
head: f7a3080ba37b989ad2fd83054a4b458af97b635d
commit: 92fe4dbd22e7faafad04ddf06d732e336ea7be98 [34/68] Rust: io: Add memcpy_fromio wrapper
config: x86_64-randconfig-073-20260404 (https://download.01.org/0day-ci/archive/20260405/202604051411.VGXONaOa-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/20260405/202604051411.VGXONaOa-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/202604051411.VGXONaOa-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0061]: this function takes 1 argument but 2 arguments were supplied
--> rust/doctests_kernel_generated.rs:7240:22
|
7240 | let devres_mem = IoMem::<100>::new(res, device)?;
| ^^^^^^^^^^^^^^^^^ ------ unexpected argument #2
|
note: associated function defined here
--> rust/kernel/io/mem.rs:267:12
|
267 | pub fn new<'a>(io_request: IoRequest<'a>) -> impl PinInit<Devres<Self>, Error> + 'a {
| ^^^
help: remove the extra argument
|
7240 - let devres_mem = IoMem::<100>::new(res, device)?;
7240 + let devres_mem = IoMem::<100>::new(res)?;
|
--
>> error[E0277]: the `?` operator can only be applied to values that implement `Try`
--> rust/doctests_kernel_generated.rs:7240:22
|
7240 | let devres_mem = IoMem::<100>::new(res, device)?;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the `?` operator cannot be applied to type `impl PinInit<Devres<IoMem<100>>, Error>`
|
= help: the trait `Try` is not implemented for `impl PinInit<Devres<IoMem<100>>, Error>`
= note: the full name for the type has been written to 'rust/doctests_kernel_generated.long-type-17116501122076988537.txt'
= note: consider using `--verbose` to print the full type name to the console
--
>> error[E0412]: cannot find type `Device` in this scope
--> rust/doctests_kernel_generated.rs:7238:18
|
7238 | fn test(device: &Device, res: Resource) -> Result {
| ^^^^^^ not found in this scope
|
help: consider importing one of these items
|
3 + use kernel::auxiliary::Device;
|
3 + use kernel::device::Device;
|
3 + use kernel::dma::Device;
|
3 + use kernel::drm::Device;
|
and 2 other candidates
--
>> error[E0603]: struct `Resource` is private
--> rust/doctests_kernel_generated.rs:7236:22
|
7236 | use kernel::io::mem::Resource;
| ^^^^^^^^ private struct
|
note: the struct `Resource` is defined here
--> rust/kernel/io/mem.rs:20:13
|
20 | Resource, //
| ^^^^^^^^
help: import `Resource` directly
|
7236 - use kernel::io::mem::Resource;
7236 + use kernel::io::resource::Resource;
|
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-07 3:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202604051411.VGXONaOa-lkp@intel.com \
--to=lkp@intel.com \
--cc=j@jannau.net \
--cc=lina@asahilina.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.