From: kernel test robot <lkp@intel.com>
To: Gary Guo <gary@garyguo.net>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: warning: doc list item overindented
Date: Fri, 15 May 2026 22:20:44 +0200 [thread overview]
Message-ID: <202605152201.ZkqCAPW9-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Gary-Guo/rust-pin-init-internal-pin_data-use-closure-for-handle_field/20260515-173849
head: 5026f92099ca080254d4263e0a554e1b040b7c16
commit: ddbf85f3617b01bc6878e1d7a05c139a69d27f7a rust: pin-init: internal: project slots instead of references
date: 11 hours ago
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260515/202605152201.ZkqCAPW9-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/20260515/202605152201.ZkqCAPW9-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/202605152201.ZkqCAPW9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> warning: doc list item overindented
--> rust/pin-init/src/__internal.rs:269:9
|
269 | /// memory.
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
= note: `-W clippy::doc-overindented-list-items` implied by `-W clippy::all`
= help: to override `-W clippy::all` add `#[allow(clippy::doc_overindented_list_items)]`
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-15 20:21 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=202605152201.ZkqCAPW9-lkp@intel.com \
--to=lkp@intel.com \
--cc=gary@garyguo.net \
--cc=oe-kbuild-all@lists.linux.dev \
/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.