public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andreas Hindborg <nmi@metaspace.dk>, Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
	Damien Le Moal <Damien.LeMoal@wdc.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Hannes Reinecke <hare@suse.de>, Ming Lei <ming.lei@redhat.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
	"Andreas Hindborg" <a.hindborg@samsung.com>,
	"Wedson Almeida Filho" <wedsonaf@gmail.com>,
	"Greg KH" <greg@kroah.com>,
	"Matthew Wilcox" <willy@infradead.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Chaitanya Kulkarni" <chaitanyak@nvidia.com>,
	"Luis Chamberlain" <mcgrof@kernel.org>,
	"Yexuan Yang" <1182282462@bupt.edu.cn>,
	"Sergio González Collado" <sergio.collado@gmail.com>,
	"Joel Granados" <j.granados@samsung.com>,
	"Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>,
	"Daniel Gomez" <da.gomez@samsung.com>,
	"Niklas Cassel" <Niklas.Cassel@wdc.com>,
	"Philipp Stanner" <pstanner@redhat.com>,
	"Conor Dooley" <conor@kernel.org>,
	"Johannes Thumshirn" <Johannes.Thumshirn@wdc.com>
Subject: Re: [PATCH 1/3] rust: block: introduce `kernel::block::mq` module
Date: Mon, 13 May 2024 19:58:19 +0800	[thread overview]
Message-ID: <202405131926.5TqIqaTc-lkp@intel.com> (raw)
In-Reply-To: <20240512183950.1982353-2-nmi@metaspace.dk>

Hi Andreas,

kernel test robot noticed the following build warnings:

[auto build test WARNING on fec50db7033ea478773b159e0e2efb135270e3b7]

url:    https://github.com/intel-lab-lkp/linux/commits/Andreas-Hindborg/rust-block-introduce-kernel-block-mq-module/20240513-024107
base:   fec50db7033ea478773b159e0e2efb135270e3b7
patch link:    https://lore.kernel.org/r/20240512183950.1982353-2-nmi%40metaspace.dk
patch subject: [PATCH 1/3] rust: block: introduce `kernel::block::mq` module
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240513/202405131926.5TqIqaTc-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/20240513/202405131926.5TqIqaTc-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/202405131926.5TqIqaTc-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> warning: unresolved link to `GenDisk`
   --> rust/kernel/block/mq.rs:10:18
   |
   10 | //! - Create a [`GenDisk<T>`], passing in the `TagSet` reference
   |                  ^^^^^^^^^^ no item named `GenDisk` 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 `GenDisk::add`
   --> rust/kernel/block/mq.rs:11:47
   |
   11 | //! - Add the disk to the system by calling [`GenDisk::add`]
   |                                               ^^^^^^^^^^^^ no item named `GenDisk` in scope
--
>> warning: unresolved link to `Operations::RequestData`
   --> rust/kernel/block/mq.rs:22:45
   |
   22 | //! associated types in `Operations`, see [`Operations::RequestData`] for an
   |                                             ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Operations` has no associated item named `RequestData`
--
>> warning: unresolved link to `Request::start`
   --> rust/kernel/block/mq.rs:30:51
   |
   30 | //! mark start of request processing by calling [`Request::start`] and end of
   |                                                   ^^^^^^^^^^^^^^ the struct `Request` has no field or associated item named `start`
--
>> warning: unresolved link to `Request::end`
   --> rust/kernel/block/mq.rs:31:40
   |
   31 | //! processing by calling one of the [`Request::end`], methods. Failure to do so
   |                                        ^^^^^^^^^^^^ the struct `Request` has no field or associated item named `end`

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

  reply	other threads:[~2024-05-13 11:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12 18:39 [PATCH 0/3] Rust block device driver API and null block driver Andreas Hindborg
2024-05-12 18:39 ` [PATCH 1/3] rust: block: introduce `kernel::block::mq` module Andreas Hindborg
2024-05-13 11:58   ` kernel test robot [this message]
2024-05-13 12:22   ` Bart Van Assche
2024-05-13 12:48     ` Andreas Hindborg
2024-05-13 13:08       ` Damien Le Moal
2024-05-13 21:13   ` kernel test robot
2024-05-12 18:39 ` [PATCH 2/3] rust: block: add rnull, Rust null_blk implementation Andreas Hindborg
2024-05-12 18:39 ` [PATCH 3/3] MAINTAINERS: add entry for Rust block device driver API Andreas Hindborg
2024-05-14 20:00 ` [PATCH 0/3] Rust block device driver API and null block driver Jens Axboe

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=202405131926.5TqIqaTc-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=1182282462@bupt.edu.cn \
    --cc=Damien.LeMoal@wdc.com \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=Niklas.Cassel@wdc.com \
    --cc=a.hindborg@samsung.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=axboe@kernel.dk \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=bvanassche@acm.org \
    --cc=chaitanyak@nvidia.com \
    --cc=conor@kernel.org \
    --cc=da.gomez@samsung.com \
    --cc=gary@garyguo.net \
    --cc=greg@kroah.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=j.granados@samsung.com \
    --cc=kbusch@kernel.org \
    --cc=kernel@pankajraghav.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=nmi@metaspace.dk \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=pstanner@redhat.com \
    --cc=sergio.collado@gmail.com \
    --cc=wedsonaf@gmail.com \
    --cc=willy@infradead.org \
    /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