From: kernel test robot <lkp@intel.com>
To: "Malte Wechter" <maltewechter@gmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Breno Leitao" <leitao@debian.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Jens Axboe" <axboe@kernel.dk>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org, linux-block@vger.kernel.org,
Malte Wechter <maltewechter@gmail.com>
Subject: Re: [PATCH] rust: add procedural macro for declaring configfs attributes
Date: Wed, 20 May 2026 18:55:27 +0200 [thread overview]
Message-ID: <202605201854.YArCKAtw-lkp@intel.com> (raw)
In-Reply-To: <20260520-configfs-syn-v1-1-6c5b80a9cef2@gmail.com>
Hi Malte,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 254f49634ee16a731174d2ae34bc50bd5f45e731]
url: https://github.com/intel-lab-lkp/linux/commits/Malte-Wechter/rust-add-procedural-macro-for-declaring-configfs-attributes/20260520-154816
base: 254f49634ee16a731174d2ae34bc50bd5f45e731
patch link: https://lore.kernel.org/r/20260520-configfs-syn-v1-1-6c5b80a9cef2%40gmail.com
patch subject: [PATCH] rust: add procedural macro for declaring configfs attributes
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260520/202605201854.YArCKAtw-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/20260520/202605201854.YArCKAtw-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/202605201854.YArCKAtw-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> warning: unclosed HTML tag `Configuration`
--> rust/macros/lib.rs:561:30
|
561 | /// Subsystem<Configuration>,
| ^^^^^^^^^^^^^^^
|
= note: `#[warn(rustdoc::invalid_html_tags)]` on by default
help: try marking as source code
|
561 | /// `Subsystem<Configuration>`,
| + +
--
>> warning: unclosed HTML tag `Configuration`
--> rust/macros/lib.rs:564:30
|
564 | /// Subsystem<Configuration>,
| ^^^^^^^^^^^^^^^
|
help: try marking as source code
|
564 | /// `Subsystem<Configuration>`,
| + +
--
>> warning: unresolved link to `crate::configfs_attrs`
--> rust/kernel/configfs.rs:240:1
|
240 | / /// A configfs group.
241 | | ///
242 | | /// To add a subgroup to configfs, pass this type as `ctype` to
243 | | /// [`crate::configfs_attrs`] when creating a group in [`GroupOperations::make_group`].
| |_______________________________________________________________________________________^
|
= note: the link appears in this line:
--
>> warning: unresolved link to `kernel::configfs_attrs`
--> rust/kernel/configfs.rs:630:1
|
630 | / /// Operations supported by an attribute.
631 | | ///
632 | | /// Implement this trait on type and pass that type as generic parameter when
633 | | /// creating an [`Attribute`]. The type carrying the implementation serve no
... |
640 | | /// attributes via the [`kernel::configfs_attrs`] macro, to tie
641 | | /// `AttributeOperations` implementations to concrete named attributes.
| |_______________________________________________________________________^
|
= note: the link appears in this line:
--
>> warning: unresolved link to `kernel::configfs_attrs`
--> rust/kernel/configfs.rs:672:7
|
672 | /// [`kernel::configfs_attrs`] macro to declare a static set of attributes for a
| ^^^^^^^^^^^^^^^^^^^^^^ no item named `configfs_attrs` in module `kernel`
--
>> warning: unresolved link to `kernel::configfs_attrs`
--> rust/kernel/configfs.rs:678:7
|
678 | /// [`kernel::configfs_attrs`] macro.
| ^^^^^^^^^^^^^^^^^^^^^^ no item named `configfs_attrs` in module `kernel`
--
>> warning: unresolved link to `kernel::configfs_attrs`
--> rust/kernel/configfs.rs:723:1
|
723 | / /// A representation of the attributes that will appear in a [`Group`] or
724 | | /// [`Subsystem`].
725 | | ///
726 | | /// Users should not directly instantiate objects of this type. Rather, they
727 | | /// should use the [`kernel::configfs_attrs`] macro to statically declare the
728 | | /// shape of a [`Group`] or [`Subsystem`].
| |__________________________________________^
|
= note: the link appears in this line:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-05-20 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 7:40 [PATCH] rust: add procedural macro for declaring configfs attributes Malte Wechter
2026-05-20 16:55 ` kernel test robot [this message]
2026-05-21 5:49 ` Gary Guo
2026-05-22 6:20 ` Andreas Hindborg
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=202605201854.YArCKAtw-lkp@intel.com \
--to=lkp@intel.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=axboe@kernel.dk \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=leitao@debian.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=maltewechter@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox