kbuild Development List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andreas Hindborg <a.hindborg@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [da-gomez:rxarray-wip 58/132] warning: unresolved link to `Segemnt`
Date: Thu, 10 Sep 2026 17:39:18 +0200	[thread overview]
Message-ID: <202609092139.HyMTlycE-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/da.gomez/linux.git rxarray-wip
head:   e9093bf6ee3dc1f9a4e2b08695a8d492d96f4ffb
commit: 366f35da2daf6243954c084c489a0ac8313c08c4 [58/132] block: rust: introduce `kernel::block::bio` module
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260909/202609092139.HyMTlycE-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/20260909/202609092139.HyMTlycE-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/202609092139.HyMTlycE-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> warning: unresolved link to `Segemnt`
   --> rust/kernel/block/bio/vec.rs:41:9
   |
   41 | /// A [`Segemnt`] is a wrapper around a `strutct bio_vec`.
   |         ^^^^^^^ no item named `Segemnt` in scope
   |
   = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
   = note: `#[warn(rustdoc::broken_intra_doc_links)]` on by default
--
>> warning: unresolved link to `Page`
   --> rust/kernel/block/bio.rs:31:7
   |
   31 | /// [`Page`] descriptors internally.
   |       ^^^^ no item named `Page` in scope
   |
   = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
--
>> warning: unresolved link to `SegmentIterator`
   --> rust/kernel/block/bio.rs:33:65
   |
   33 | /// The vector of [`Segment`]s can be iterated by obtaining a [`SegmentIterator`].
   |                                                                 ^^^^^^^^^^^^^^^ no item named `SegmentIterator` in scope
   |
   = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`

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

                 reply	other threads:[~2026-09-10 15:39 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=202609092139.HyMTlycE-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=a.hindborg@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox