public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Zhi Wang <zhiw@nvidia.com>,
	rust-for-linux@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	dakr@kernel.org, aliceryhl@google.com, bhelgaas@google.com,
	kwilczynski@kernel.org, ojeda@kernel.org, alex.gaynor@gmail.com,
	boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com,
	lossin@kernel.org, a.hindborg@kernel.org, tmgross@umich.edu,
	markus.probst@posteo.de, helgaas@kernel.org, cjia@nvidia.com,
	smitra@nvidia.com, ankita@nvidia.com, aniketa@nvidia.com,
	kwankhede@nvidia.com, targupta@nvidia.com, acourbot@nvidia.com,
	joelagnelf@nvidia.com, jhubbard@nvidia.com, zhiwang@kernel.org,
	daniel.almeida@collabora.com, Zhi Wang <zhiw@nvidia.com>
Subject: Re: [PATCH v10 2/5] rust: io: separate generic I/O helpers from MMIO implementation
Date: Tue, 20 Jan 2026 21:37:11 +0800	[thread overview]
Message-ID: <202601202126.NVP5cs8k-lkp@intel.com> (raw)
In-Reply-To: <20260119202250.870588-3-zhiw@nvidia.com>

Hi Zhi,

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]
[cannot apply to driver-core/driver-core-linus pci/next pci/for-linus drm-rust/drm-rust-next linus/master v6.19-rc6 next-20260119]
[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/Zhi-Wang/rust-devres-style-for-imports/20260120-042526
base:   driver-core/driver-core-testing
patch link:    https://lore.kernel.org/r/20260119202250.870588-3-zhiw%40nvidia.com
patch subject: [PATCH v10 2/5] rust: io: separate generic I/O helpers from MMIO implementation
config: x86_64-buildonly-randconfig-004-20260120 (https://download.01.org/0day-ci/archive/20260120/202601202126.NVP5cs8k-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/20260120/202601202126.NVP5cs8k-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/202601202126.NVP5cs8k-lkp@intel.com/

All errors (new ones prefixed by >>):

>> error[E0599]: no method named `try_read32` found for reference `&Mmio<176>` in the current scope
   --> drivers/pwm/pwm_th1520.rs:241:26
   |
   241 |         let ctrl = iomap.try_read32(th1520_pwm_ctrl(hwpwm))?;
   |                          ^^^^^^^^^^
   |
   = help: items from traits can only be used if the trait is in scope
   help: trait `Io` which provides `try_read32` is implemented but not in scope; perhaps you want to import it
   |
   23  + use kernel::io::Io;
   |
   help: there is a method `try_read` with a similar name
   |
   241 -         let ctrl = iomap.try_read32(th1520_pwm_ctrl(hwpwm))?;
   241 +         let ctrl = iomap.try_read(th1520_pwm_ctrl(hwpwm))?;
   |
--
>> error[E0599]: no method named `try_read32` found for reference `&Mmio<176>` in the current scope
   --> drivers/pwm/pwm_th1520.rs:242:35
   |
   242 |         let period_cycles = iomap.try_read32(th1520_pwm_per(hwpwm))?;
   |                                   ^^^^^^^^^^
   |
   = help: items from traits can only be used if the trait is in scope
   help: trait `Io` which provides `try_read32` is implemented but not in scope; perhaps you want to import it
   |
   23  + use kernel::io::Io;
   |
   help: there is a method `try_read` with a similar name
   |
   242 -         let period_cycles = iomap.try_read32(th1520_pwm_per(hwpwm))?;
   242 +         let period_cycles = iomap.try_read(th1520_pwm_per(hwpwm))?;
   |
--
>> error[E0599]: no method named `try_write32` found for reference `&Mmio<176>` in the current scope
   --> drivers/pwm/pwm_th1520.rs:294:15
   |
   294 |         iomap.try_write32(
   |         ------^^^^^^^^^^^
   |
   = help: items from traits can only be used if the trait is in scope
   help: trait `Io` which provides `try_write32` is implemented but not in scope; perhaps you want to import it
   |
   23  + use kernel::io::Io;
   |
   help: there is a method `try_write` with a similar name
   |
   294 -         iomap.try_write32(
   294 +         iomap.try_write(
   |
--
>> error[E0599]: no method named `try_write32` found for reference `&Mmio<176>` in the current scope
   --> drivers/pwm/pwm_th1520.rs:302:19
   |
   302 |             iomap.try_write32(wfhw.ctrl_val | TH1520_PWM_START, th1520_pwm_ctrl(hwpwm))?;
   |                   ^^^^^^^^^^^
   |
   = help: items from traits can only be used if the trait is in scope
   help: trait `Io` which provides `try_write32` is implemented but not in scope; perhaps you want to import it
   |
   23  + use kernel::io::Io;
   |
   help: there is a method `try_write` with a similar name
   |
   302 -             iomap.try_write32(wfhw.ctrl_val | TH1520_PWM_START, th1520_pwm_ctrl(hwpwm))?;
   302 +             iomap.try_write(wfhw.ctrl_val | TH1520_PWM_START, th1520_pwm_ctrl(hwpwm))?;
   |
--
>> error[E0599]: no method named `try_read32` found for reference `&Mmio<176>` in the current scope
   --> drivers/pwm/pwm_th1520.rs:243:33
   |
   243 |         let duty_cycles = iomap.try_read32(th1520_pwm_fp(hwpwm))?;
   |                                 ^^^^^^^^^^
   |
   = help: items from traits can only be used if the trait is in scope
   help: trait `Io` which provides `try_read32` is implemented but not in scope; perhaps you want to import it
   |
   23  + use kernel::io::Io;
   |
   help: there is a method `try_read` with a similar name
   |
   243 -         let duty_cycles = iomap.try_read32(th1520_pwm_fp(hwpwm))?;
   243 +         let duty_cycles = iomap.try_read(th1520_pwm_fp(hwpwm))?;
   |
--
>> error[E0599]: no method named `try_read32` found for reference `&Mmio<176>` in the current scope
   --> drivers/pwm/pwm_th1520.rs:275:33
   |
   275 |         let duty_cycles = iomap.try_read32(th1520_pwm_fp(hwpwm))?;
   |                                 ^^^^^^^^^^
   |
   = help: items from traits can only be used if the trait is in scope
   help: trait `Io` which provides `try_read32` is implemented but not in scope; perhaps you want to import it
   |
   23  + use kernel::io::Io;
   |
   help: there is a method `try_read` with a similar name
   |
   275 -         let duty_cycles = iomap.try_read32(th1520_pwm_fp(hwpwm))?;
   275 +         let duty_cycles = iomap.try_read(th1520_pwm_fp(hwpwm))?;
   |
--
>> error[E0599]: no method named `try_write32` found for reference `&Mmio<176>` in the current scope
   --> drivers/pwm/pwm_th1520.rs:281:23
   |
   281 |                 iomap.try_write32(wfhw.ctrl_val, th1520_pwm_ctrl(hwpwm))?;
   |                       ^^^^^^^^^^^
   |
   = help: items from traits can only be used if the trait is in scope
   help: trait `Io` which provides `try_write32` is implemented but not in scope; perhaps you want to import it
   |
   23  + use kernel::io::Io;
   |
   help: there is a method `try_write` with a similar name
   |
   281 -                 iomap.try_write32(wfhw.ctrl_val, th1520_pwm_ctrl(hwpwm))?;
   281 +                 iomap.try_write(wfhw.ctrl_val, th1520_pwm_ctrl(hwpwm))?;
   |
--
>> error[E0599]: no method named `try_write32` found for reference `&Mmio<176>` in the current scope
   --> drivers/pwm/pwm_th1520.rs:282:23
   |
   282 |                 iomap.try_write32(0, th1520_pwm_fp(hwpwm))?;
   |                       ^^^^^^^^^^^
   |
   = help: items from traits can only be used if the trait is in scope
   help: trait `Io` which provides `try_write32` is implemented but not in scope; perhaps you want to import it
   |
   23  + use kernel::io::Io;
   |
   help: there is a method `try_write` with a similar name
   |
   282 -                 iomap.try_write32(0, th1520_pwm_fp(hwpwm))?;
   282 +                 iomap.try_write(0, th1520_pwm_fp(hwpwm))?;
   |
--
>> error[E0599]: no method named `try_write32` found for reference `&Mmio<176>` in the current scope
   --> drivers/pwm/pwm_th1520.rs:283:23
   |
   283 |                 iomap.try_write32(
   |                 ------^^^^^^^^^^^
   |
   = help: items from traits can only be used if the trait is in scope
   help: trait `Io` which provides `try_write32` is implemented but not in scope; perhaps you want to import it
   |
   23  + use kernel::io::Io;
   |
   help: there is a method `try_write` with a similar name
   |
   283 -                 iomap.try_write32(
   283 +                 iomap.try_write(
   |
--
>> error[E0599]: no method named `try_write32` found for reference `&Mmio<176>` in the current scope
   --> drivers/pwm/pwm_th1520.rs:291:15
   |
   291 |         iomap.try_write32(wfhw.ctrl_val, th1520_pwm_ctrl(hwpwm))?;
   |               ^^^^^^^^^^^
   |
   = help: items from traits can only be used if the trait is in scope
   help: trait `Io` which provides `try_write32` is implemented but not in scope; perhaps you want to import it
   |
   23  + use kernel::io::Io;
   |
   help: there is a method `try_write` with a similar name
   |
   291 -         iomap.try_write32(wfhw.ctrl_val, th1520_pwm_ctrl(hwpwm))?;
   291 +         iomap.try_write(wfhw.ctrl_val, th1520_pwm_ctrl(hwpwm))?;
   |
--
>> error[E0599]: no method named `try_write32` found for reference `&Mmio<176>` in the current scope
   --> drivers/pwm/pwm_th1520.rs:292:15
   |
   292 |         iomap.try_write32(wfhw.period_cycles, th1520_pwm_per(hwpwm))?;
   |               ^^^^^^^^^^^
   |
   = help: items from traits can only be used if the trait is in scope
   help: trait `Io` which provides `try_write32` is implemented but not in scope; perhaps you want to import it
   |
   23  + use kernel::io::Io;
   |
   help: there is a method `try_write` with a similar name
   |
   292 -         iomap.try_write32(wfhw.period_cycles, th1520_pwm_per(hwpwm))?;
   292 +         iomap.try_write(wfhw.period_cycles, th1520_pwm_per(hwpwm))?;
   |
..

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

  parent reply	other threads:[~2026-01-20 13:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 20:22 [PATCH v10 0/5] rust: pci: add config space read/write support Zhi Wang
2026-01-19 20:22 ` [PATCH v10 1/5] rust: devres: style for imports Zhi Wang
2026-01-20 15:26   ` Gary Guo
2026-01-20 16:11   ` Miguel Ojeda
2026-01-21  9:29     ` Zhi Wang
2026-01-22  1:55       ` Miguel Ojeda
2026-01-22  2:24         ` John Hubbard
2026-01-22 11:43           ` Danilo Krummrich
2026-01-19 20:22 ` [PATCH v10 2/5] rust: io: separate generic I/O helpers from MMIO implementation Zhi Wang
2026-01-20  8:04   ` Alice Ryhl
2026-01-20 10:12     ` Danilo Krummrich
2026-01-20 11:26       ` Alice Ryhl
2026-01-20 12:38         ` Alice Ryhl
2026-01-20 15:59       ` Gary Guo
2026-01-20 16:09         ` Danilo Krummrich
2026-01-20 17:26       ` Zhi Wang
2026-01-20 17:29         ` Danilo Krummrich
2026-01-20 17:35         ` Gary Guo
2026-01-20 13:37   ` kernel test robot [this message]
2026-01-20 15:54   ` Gary Guo
2026-01-19 20:22 ` [PATCH v10 3/5] rust: io: factor out MMIO read/write macros Zhi Wang
2026-01-19 20:22 ` [PATCH v10 4/5] rust: pci: add config space read/write support Zhi Wang
2026-01-19 20:22 ` [PATCH v10 5/5] sample: rust: pci: add tests for config space routines Zhi Wang

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=202601202126.NVP5cs8k-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=aniketa@nvidia.com \
    --cc=ankita@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=cjia@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=gary@garyguo.net \
    --cc=helgaas@kernel.org \
    --cc=jhubbard@nvidia.com \
    --cc=joelagnelf@nvidia.com \
    --cc=kwankhede@nvidia.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=lossin@kernel.org \
    --cc=markus.probst@posteo.de \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=smitra@nvidia.com \
    --cc=targupta@nvidia.com \
    --cc=tmgross@umich.edu \
    --cc=zhiw@nvidia.com \
    --cc=zhiwang@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