All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Daniel Almeida" <daniel.almeida@collabora.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>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	Daniel Almeida <daniel.almeida@collabora.com>
Subject: Re: [PATCH] rust: irq: add support for request_irq()
Date: Sun, 27 Oct 2024 13:30:16 +0800	[thread overview]
Message-ID: <202410271331.Kh0GAuXf-lkp@intel.com> (raw)
In-Reply-To: <20241024-topic-panthor-rs-request_irq-v1-1-7cbc51c182ca@collabora.com>

Hi Daniel,

kernel test robot noticed the following build errors:

[auto build test ERROR on 33c255312660653cf54f8019896b5dca28e3c580]

url:    https://github.com/intel-lab-lkp/linux/commits/Daniel-Almeida/rust-irq-add-support-for-request_irq/20241024-222633
base:   33c255312660653cf54f8019896b5dca28e3c580
patch link:    https://lore.kernel.org/r/20241024-topic-panthor-rs-request_irq-v1-1-7cbc51c182ca%40collabora.com
patch subject: [PATCH] rust: irq: add support for request_irq()
config: riscv-randconfig-001-20241027 (https://download.01.org/0day-ci/archive/20241027/202410271331.Kh0GAuXf-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241027/202410271331.Kh0GAuXf-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/202410271331.Kh0GAuXf-lkp@intel.com/

All errors (new ones prefixed by >>):

>> error[E0432]: unresolved import `kernel::irq::Registration`
   --> rust/doctests_kernel_generated.rs:1837:5
   |
   1837 | use kernel::irq::Registration;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ no `Registration` in `irq`
   |
   help: consider importing one of these items instead
   |
   1837 | use kernel::irq::request::Registration;
   |     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   1837 | use kernel::net::phy::Registration;
   |     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
>> error[E0432]: unresolved import `kernel::sync::lock::SpinLock`
   --> rust/doctests_kernel_generated.rs:1839:5
   |
   1839 | use kernel::sync::lock::SpinLock;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `SpinLock` in `sync::lock`
   |
   help: a similar name exists in the module
   |
   1839 | use kernel::sync::lock::spinlock;
   |                         ~~~~~~~~
   help: consider importing this type alias instead
   |
   1839 | use kernel::sync::SpinLock;
   |     ~~~~~~~~~~~~~~~~~~~~~~
--
>> error[E0412]: cannot find type `ThreadedIrqReturn` in module `irq`
   --> rust/doctests_kernel_generated.rs:1955:34
   |
   1955 |     fn handle_irq(&self) -> irq::ThreadedIrqReturn {
   |                                  ^^^^^^^^^^^^^^^^^ not found in `irq`
   |
   help: consider importing this enum
   |
   3    + use kernel::irq::request::ThreadedIrqReturn;
   |
   help: if you import `ThreadedIrqReturn`, refer to it directly
   |
   1955 -     fn handle_irq(&self) -> irq::ThreadedIrqReturn {
   1955 +     fn handle_irq(&self) -> ThreadedIrqReturn {
   |
--
>> error[E0433]: failed to resolve: use of undeclared type `ThreadedIrqReturn`
   --> rust/doctests_kernel_generated.rs:1963:9
   |
   1963 |         ThreadedIrqReturn::WakeThread
   |         ^^^^^^^^^^^^^^^^^ use of undeclared type `ThreadedIrqReturn`
   |
   help: consider importing this enum
   |
   3    + use kernel::irq::request::ThreadedIrqReturn;
   |
--
>> error[E0412]: cannot find type `ThreadedFnReturn` in module `irq`
   --> rust/doctests_kernel_generated.rs:1968:33
   |
   1968 |     fn thread_fn(&self) -> irq::ThreadedFnReturn {
   |                                 ^^^^^^^^^^^^^^^^ not found in `irq`
   |
   help: consider importing this enum
   |
   3    + use kernel::irq::request::ThreadedFnReturn;
   |
   help: if you import `ThreadedFnReturn`, refer to it directly
   |
   1968 -     fn thread_fn(&self) -> irq::ThreadedFnReturn {
   1968 +     fn thread_fn(&self) -> ThreadedFnReturn {
   |
--
>> error[E0412]: cannot find type `Registration` in module `irq`
   --> rust/doctests_kernel_generated.rs:1975:64
   |
   1975 |     fn register_irq(irq: u32, handler: Handler) -> Result<irq::Registration<Handler>> {
   |                                                                ^^^^^^^^^^^^ not found in `irq`
   |
   help: consider importing one of these items
   |
   3    + use kernel::irq::request::Registration;
   |
   3    + use kernel::net::phy::Registration;
   |
   help: if you import `Registration`, refer to it directly
   |
   1975 -     fn register_irq(irq: u32, handler: Handler) -> Result<irq::Registration<Handler>> {
   1975 +     fn register_irq(irq: u32, handler: Handler) -> Result<Registration<Handler>> {
   |
--
>> error[E0433]: failed to resolve: use of undeclared type `ThreadedRegistration`
   --> rust/doctests_kernel_generated.rs:1976:28
   |
   1976 |         let registration = ThreadedRegistration::register(irq, irq::flags::SHARED, "my-device", handler)?;
   |                            ^^^^^^^^^^^^^^^^^^^^ use of undeclared type `ThreadedRegistration`
   |
   help: consider importing this struct
   |
   3    + use kernel::irq::request::ThreadedRegistration;
   |
--
>> error[E0433]: failed to resolve: could not find `flags` in `irq`
   --> rust/doctests_kernel_generated.rs:1976:69
   |
   1976 |         let registration = ThreadedRegistration::register(irq, irq::flags::SHARED, "my-device", handler)?;
   |                                                                     ^^^^^ could not find `flags` in `irq`
   |
   help: consider importing this module
   |
   3    + use kernel::irq::request::flags;
   |
   help: if you import `flags`, refer to it directly
   |
   1976 -         let registration = ThreadedRegistration::register(irq, irq::flags::SHARED, "my-device", handler)?;
   1976 +         let registration = ThreadedRegistration::register(irq, flags::SHARED, "my-device", handler)?;
   |
--
>> error[E0432]: unresolved import `kernel::irq::Registration`
   --> rust/doctests_kernel_generated.rs:1934:5
   |
   1934 | use kernel::irq::Registration;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ no `Registration` in `irq`
   |
   help: consider importing one of these items instead
   |
   1934 | use kernel::irq::request::Registration;
   |     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   1934 | use kernel::net::phy::Registration;
   |     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
>> error[E0432]: unresolved import `kernel::sync::lock::SpinLock`
   --> rust/doctests_kernel_generated.rs:1936:5
   |
   1936 | use kernel::sync::lock::SpinLock;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `SpinLock` in `sync::lock`
   |
   help: a similar name exists in the module
   |
   1936 | use kernel::sync::lock::spinlock;
   |                         ~~~~~~~~
   help: consider importing this type alias instead
   |
   1936 | use kernel::sync::SpinLock;
   |     ~~~~~~~~~~~~~~~~~~~~~~
--
>> error[E0405]: cannot find trait `Handler` in module `kernel::irq`
   --> rust/doctests_kernel_generated.rs:1855:19
   |
   1855 | impl kernel::irq::Handler for Handler {
   |                   ^^^^^^^ not found in `kernel::irq`
   |
   help: consider importing this trait
   |
   3    + use kernel::irq::request::Handler;
   |
   help: if you import `Handler`, refer to it directly
   |
   1855 - impl kernel::irq::Handler for Handler {
   1855 + impl Handler for Handler {
   |
..

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

  parent reply	other threads:[~2024-10-27  5:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 14:20 [PATCH] rust: irq: add support for request_irq() Daniel Almeida
2024-10-24 15:05 ` Miguel Ojeda
2024-10-24 15:08   ` Daniel Almeida
2024-10-27  5:30 ` kernel test robot [this message]
2024-10-28 15:29 ` Alice Ryhl
2024-11-04 20:10   ` Daniel Almeida
2024-11-06 11:17     ` Alice Ryhl
2024-10-29 11:59 ` Alice Ryhl
2024-11-04 19:19   ` Daniel Almeida
2025-01-13 14:42 ` Alice Ryhl
2025-01-14 18:34   ` Daniel Almeida
2025-01-14 18:36     ` Alice Ryhl
2025-01-14 18:57       ` Daniel Almeida
2025-01-15  0:45         ` Boqun Feng
2025-01-15  8:27           ` Alice Ryhl
2025-01-15 14:39             ` Boqun Feng
2025-01-15 14:42               ` Alice Ryhl
2025-01-15 16:00                 ` Boqun Feng
2025-01-15 15:37               ` Daniel Almeida
2025-01-15 11:38         ` Gary Guo
2025-01-15 12:31           ` Daniel Almeida
2025-01-16  8:29             ` Alice Ryhl
2025-01-19 17:50               ` Boqun Feng
2025-01-15 11:42 ` Gary Guo

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=202410271331.Kh0GAuXf-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=daniel.almeida@collabora.com \
    --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=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 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.