From: kernel test robot <lkp@intel.com>
To: Timur Tabi <ttabi@nvidia.com>,
Matthew Maurer <mmaurer@google.com>,
Danilo Krummrich <dakr@kernel.org>, Gary Guo <gary@garyguo.net>,
John Hubbard <jhubbard@nvidia.com>,
Joel Fernandes <joelagnelf@nvidia.com>,
Alexandre Courbot <acourbot@nvidia.com>,
rust-for-linux@vger.kernel.org, nouveau@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v4 5/9] rust: debugfs: implement Directory trait for Dir
Date: Fri, 16 Jan 2026 01:27:47 +0800 [thread overview]
Message-ID: <202601160158.7mf9LG1y-lkp@intel.com> (raw)
In-Reply-To: <20260113225408.671252-6-ttabi@nvidia.com>
Hi Timur,
kernel test robot noticed the following build errors:
[auto build test ERROR on 654826aa4a8f25cf825ad9254f37e6cb5092098f]
url: https://github.com/intel-lab-lkp/linux/commits/Timur-Tabi/rust-pci-add-PCI-device-name-method/20260114-065717
base: 654826aa4a8f25cf825ad9254f37e6cb5092098f
patch link: https://lore.kernel.org/r/20260113225408.671252-6-ttabi%40nvidia.com
patch subject: [PATCH v4 5/9] rust: debugfs: implement Directory trait for Dir
config: x86_64-randconfig-122-20260114 (https://download.01.org/0day-ci/archive/20260116/202601160158.7mf9LG1y-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/20260116/202601160158.7mf9LG1y-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/202601160158.7mf9LG1y-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0599]: no function or associated item named `new` found for struct `Dir` in the current scope
--> rust/doctests_kernel_generated.rs:4085:16
|
4085 | let dir = Dir::new(c_str!("my_debugfs_dir"));
| ^^^ function or associated item not found in `Dir`
|
= help: items from traits can only be used if the trait is in scope
help: trait `Directory` which provides `new` is implemented but not in scope; perhaps you want to import it
|
3 + use crate::rust_doctest_kernel_alloc_allocator_rs_0::kernel::debugfs::Directory;
|
--
>> error[E0599]: no function or associated item named `new` found for struct `Dir` in the current scope
--> rust/doctests_kernel_generated.rs:4145:16
|
4145 | let dir = Dir::new(c_str!("my_debugfs_dir"));
| ^^^ function or associated item not found in `Dir`
|
= help: items from traits can only be used if the trait is in scope
help: trait `Directory` which provides `new` is implemented but not in scope; perhaps you want to import it
|
3 + use crate::rust_doctest_kernel_alloc_allocator_rs_0::kernel::debugfs::Directory;
|
--
>> error[E0599]: no function or associated item named `new` found for struct `Dir` in the current scope
--> rust/doctests_kernel_generated.rs:4204:16
|
4204 | let dir = Dir::new(c_str!("foo"));
| ^^^ function or associated item not found in `Dir`
|
= help: items from traits can only be used if the trait is in scope
help: trait `Directory` which provides `new` is implemented but not in scope; perhaps you want to import it
|
3 + use crate::rust_doctest_kernel_alloc_allocator_rs_0::kernel::debugfs::Directory;
|
--
>> error[E0599]: no function or associated item named `new` found for struct `Dir` in the current scope
--> rust/doctests_kernel_generated.rs:3973:20
|
3973 | let debugfs = Dir::new(c_str!("parent"));
| ^^^ function or associated item not found in `Dir`
|
= help: items from traits can only be used if the trait is in scope
help: trait `Directory` which provides `new` is implemented but not in scope; perhaps you want to import it
|
3 + use crate::rust_doctest_kernel_alloc_allocator_rs_0::kernel::debugfs::Directory;
|
--
>> error[E0599]: no function or associated item named `new` found for struct `Dir` in the current scope
--> rust/doctests_kernel_generated.rs:4028:19
|
4028 | let parent = Dir::new(c_str!("parent"));
| ^^^ function or associated item not found in `Dir`
|
= help: items from traits can only be used if the trait is in scope
help: trait `Directory` which provides `new` is implemented but not in scope; perhaps you want to import it
|
3 + use crate::rust_doctest_kernel_alloc_allocator_rs_0::kernel::debugfs::Directory;
|
--
>> error[E0599]: no function or associated item named `new` found for struct `Dir` in the current scope
--> rust/doctests_kernel_generated.rs:11462:20
|
11462 | let dir = Dir::new(pdev.name());
| ^^^ function or associated item not found in `Dir`
|
= help: items from traits can only be used if the trait is in scope
help: trait `Directory` which provides `new` is implemented but not in scope; perhaps you want to import it
|
3 + use crate::rust_doctest_kernel_alloc_allocator_rs_0::kernel::debugfs::Directory;
|
--
>> error[E0599]: no function or associated item named `new` found for struct `Dir` in the current scope
--> samples/rust/rust_debugfs.rs:136:28
|
136 | let debugfs = Dir::new(c_str!("sample_debugfs"));
| ^^^ function or associated item not found in `Dir`
|
= help: items from traits can only be used if the trait is in scope
help: trait `Directory` which provides `new` is implemented but not in scope; perhaps you want to import it
|
34 + use kernel::debugfs::Directory;
|
--
>> error[E0599]: no function or associated item named `new` found for struct `Dir` in the current scope
--> samples/rust/rust_debugfs_scoped.rs:134:29
|
134 | let base_dir = Dir::new(c_str!("rust_scoped_debugfs"));
| ^^^ function or associated item not found in `Dir`
|
= help: items from traits can only be used if the trait is in scope
help: trait `Directory` which provides `new` is implemented but not in scope; perhaps you want to import it
|
9 + use kernel::debugfs::Directory;
|
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-15 17:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 22:53 [PATCH v4 0/9] gpu: nova-core: expose the logging buffers via debugfs Timur Tabi
2026-01-13 22:54 ` [PATCH v4 1/9] rust: pci: add PCI device name method Timur Tabi
2026-01-13 22:54 ` [PATCH v4 2/9] gpu: nova-core: implement BinaryWriter for LogBuffer Timur Tabi
2026-01-13 22:54 ` [PATCH v4 3/9] gpu: nova-core: Replace module_pci_driver! with explicit module init Timur Tabi
2026-01-13 22:54 ` [PATCH v4 4/9] gpu: nova-core: use pin projection in method boot() Timur Tabi
2026-01-13 22:54 ` [PATCH v4 5/9] rust: debugfs: implement Directory trait for Dir Timur Tabi
2026-01-15 17:27 ` kernel test robot [this message]
2026-01-13 22:54 ` [PATCH v4 6/9] rust: debugfs: wrap Entry in an enum to prep for LookupDir Timur Tabi
2026-01-13 22:54 ` [PATCH v4 7/9] rust: debugfs: add LookupDir Timur Tabi
2026-01-13 22:54 ` [PATCH v4 8/9] gpu: nova-core: create debugfs root when driver loads Timur Tabi
2026-01-13 22:54 ` [PATCH v4 9/9] gpu: nova-core: create GSP-RM logging buffers debugfs entries Timur Tabi
2026-01-13 23:11 ` [PATCH v4 0/9] gpu: nova-core: expose the logging buffers via debugfs Danilo Krummrich
2026-01-13 23:26 ` Timur Tabi
2026-01-13 23:50 ` Danilo Krummrich
2026-01-13 23:59 ` Timur Tabi
2026-01-14 1:09 ` Gary Guo
2026-01-14 11:17 ` Danilo Krummrich
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=202601160158.7mf9LG1y-lkp@intel.com \
--to=lkp@intel.com \
--cc=acourbot@nvidia.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=mmaurer@google.com \
--cc=nouveau@lists.freedesktop.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=ttabi@nvidia.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