From: kernel test robot <lkp@intel.com>
To: Moayad Salloum <salloummoayad4@gmail.com>,
rust-for-linux@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, ojeda@kernel.org,
aliceryhl@google.com, lossin@kernel.org, a.hindborg@kernel.org,
Moayad Salloum <salloummoayad4@gmail.com>
Subject: Re: [PATCH] rust: workqueue: add cancel_work for Arc<T>
Date: Tue, 19 May 2026 03:46:02 +0800 [thread overview]
Message-ID: <202605190332.rlkguvbn-lkp@intel.com> (raw)
In-Reply-To: <20260518042347.95213-1-salloummoayad4@gmail.com>
Hi Moayad,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rust/rust-next]
[also build test WARNING on linus/master v7.1-rc4 next-20260518]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Moayad-Salloum/rust-workqueue-add-cancel_work-for-Arc-T/20260518-122747
base: https://github.com/Rust-for-Linux/linux rust-next
patch link: https://lore.kernel.org/r/20260518042347.95213-1-salloummoayad4%40gmail.com
patch subject: [PATCH] rust: workqueue: add cancel_work for Arc<T>
config: x86_64-randconfig-011-20260518 (https://download.01.org/0day-ci/archive/20260519/202605190332.rlkguvbn-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/20260519/202605190332.rlkguvbn-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/202605190332.rlkguvbn-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> warning: missing documentation for a function
--> rust/kernel/workqueue.rs:874:1
|
874 | / pub fn cancel_work<T, const ID: u64>(item: &Arc<T>) -> bool
875 | | where
876 | | T: WorkItem<ID, Pointer = Arc<T>>,
877 | | T: HasWork<T, ID>,
| |______________________^
|
= note: requested on the command line with `-W missing-docs`
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-05-18 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 4:23 [PATCH] rust: workqueue: add cancel_work for Arc<T> Moayad Salloum
2026-05-18 5:45 ` Onur Özkan
2026-05-18 8:10 ` kernel test robot
2026-05-18 19:46 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-18 4:11 [PATCH 1/2] rust: workqueue: add SAFETY comments for Pin<KBox<T>> impls Moayad Salloum
2026-05-18 4:11 ` [PATCH] rust: workqueue: add cancel_work for Arc<T> Moayad Salloum
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=202605190332.rlkguvbn-lkp@intel.com \
--to=lkp@intel.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lossin@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=salloummoayad4@gmail.com \
/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