From: kernel test robot <lkp@intel.com>
To: Wedson Almeida Filho <walmeida@microsoft.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Miguel Ojeda <ojeda@kernel.org>,
Danilo Krummrich <dakr@redhat.com>
Subject: [rust:staging/rust-device 5/12] error[E0425]: cannot find value `THIS_MODULE` in the crate root
Date: Sun, 16 Jun 2024 05:21:42 +0800 [thread overview]
Message-ID: <202406160537.FF7m5SCK-lkp@intel.com> (raw)
tree: https://github.com/Rust-for-Linux/linux staging/rust-device
head: 6530ecc4ac729a040a955a5e2d13c37d671b6e5c
commit: e89012e5ba8514aeff4eb4c7247d3a98025d3201 [5/12] rust: introduce `InPlaceModule`
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240616/202406160537.FF7m5SCK-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240616/202406160537.FF7m5SCK-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/202406160537.FF7m5SCK-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0425]: cannot find value `THIS_MODULE` in the crate root
--> rust/doctests_kernel_generated.rs:1649:1
|
1649 | / kernel::module_phy_driver! {
1650 | | drivers: [PhySample],
1651 | | device_table: [
1652 | | DeviceId::new_with_driver::<PhySample>()
... |
1657 | | license: "GPL",
1658 | | }
| |_^ not found in the crate root
|
= note: this error originates in the macro `$crate::prelude::module` which comes from the expansion of the macro `kernel::module_phy_driver` (in Nightly builds, run with -Z macro-backtrace for more info)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-15 21:22 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=202406160537.FF7m5SCK-lkp@intel.com \
--to=lkp@intel.com \
--cc=dakr@redhat.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=walmeida@microsoft.com \
/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;
as well as URLs for NNTP newsgroup(s).