From: kernel test robot <lkp@intel.com>
To: Alistair Popple <apopple@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jfern:nova/irq-2 33/86] warning: missing documentation for a method
Date: Sun, 27 Jul 2025 04:58:33 +0200 [thread overview]
Message-ID: <202507270419.UItjfnc4-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jfern/linux.git nova/irq-2
head: 66760845172d63f85c4edfbe93a126e71d722105
commit: ec3aa243da9f43c028ed0bd96edde9e5249a4758 [33/86] rust: Add dma_set_mask() bindings
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250727/202507270419.UItjfnc4-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/20250727/202507270419.UItjfnc4-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/202507270419.UItjfnc4-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> warning: missing documentation for a method
--> rust/kernel/pci.rs:397:5
|
397 | pub fn dma_set_mask(&self, mask: u64) -> Result {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: requested on the command line with `-W missing-docs`
--
>> warning: missing documentation for a method
--> rust/kernel/pci.rs:408:5
|
408 | pub fn dma_set_coherent_mask(&self, mask: u64) -> Result {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-27 2:59 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=202507270419.UItjfnc4-lkp@intel.com \
--to=lkp@intel.com \
--cc=apopple@nvidia.com \
--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.