Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Colin Braun <colinbrauncl@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>
Subject: [tiwai-sound:test/sound-rust-v7.3 37/56] error[E0433]: cannot find `module_usb_driver` in `kernel`
Date: Sun, 08 Nov 2026 14:18:26 +0800	[thread overview]
Message-ID: <202611081435.FPB03bH2-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git test/sound-rust-v7.3
head:   070444a8abf14da700680a5331d0a95cd11e578b
commit: 62a6ac49d75b79105edfb6f148ca23108899be6d [37/56] media: add gv-usb2 audio capture driver
config: x86_64-allmodconfig (https://download.01.org/0day-ci/archive/20261108/202611081435.FPB03bH2-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261108/202611081435.FPB03bH2-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/202611081435.FPB03bH2-lkp@intel.com/

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

>> error[E0432]: unresolved import `kernel::usb`
   --> drivers/media/usb/gv-usb2/driver.rs:17:5
   |
   17 |     usb,
   |     ^^^ no `usb` in the root
   |
   note: found an item that was configured out
   --> rust/kernel/lib.rs:148:9
   |
   147 | #[cfg(CONFIG_USB = "y")]
   |       ---------------- the item is gated behind the `y` feature
   148 | pub mod usb;
   |         ^^^
--
>> error[E0433]: cannot find `module_usb_driver` in `kernel`
   --> drivers/media/usb/gv-usb2/gv_usb2.rs:7:9
   |
   7 | kernel::module_usb_driver! {
   |         ^^^^^^^^^^^^^^^^^ could not find `module_usb_driver` in `kernel`
--
>> error[E0433]: cannot find `usb_device_table` in `kernel`
   --> drivers/media/usb/gv-usb2/driver.rs:152:9
   |
   152 | kernel::usb_device_table!(
   |         ^^^^^^^^^^^^^^^^ could not find `usb_device_table` in `kernel`
--
>> error[E0425]: cannot find value `USB_TABLE` in this scope
   --> drivers/media/usb/gv-usb2/driver.rs:162:51
   |
   162 |     const ID_TABLE: usb::IdTable<Self::IdInfo> = &USB_TABLE;
   |                                                   ^^^^^^^^^ not found in this scope
--
>> warning: unused import: `crate::driver::GvUsb2Driver`
   --> drivers/media/usb/gv-usb2/gv_usb2.rs:5:5
   |
   5 | use crate::driver::GvUsb2Driver;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default

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

                 reply	other threads:[~2026-11-08  6:19 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=202611081435.FPB03bH2-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=colinbrauncl@gmail.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tiwai@suse.de \
    /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