Rust for Linux List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Artem Lytkin <iprintercanon@gmail.com>,
	linux-watchdog@vger.kernel.org, rust-for-linux@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	wim@linux-watchdog.org, linux@roeck-us.net, ojeda@kernel.org,
	miguel.ojeda.sandonis@gmail.com, dakr@kernel.org,
	aliceryhl@google.com, a.hindborg@kernel.org, lossin@kernel.org
Subject: Re: [PATCH v2 3/3] watchdog: softdog_rs: add Rust software watchdog driver
Date: Mon, 17 Aug 2026 09:43:34 +0200	[thread overview]
Message-ID: <202608170957.oeQwdAP3-lkp@intel.com> (raw)
In-Reply-To: <20260723161529.23759-4-iprintercanon@gmail.com>

Hi Artem,

kernel test robot noticed the following build warnings:

[auto build test WARNING on rust/rust-next]
[also build test WARNING on linus/master v7.2 next-20260721]
[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/Artem-Lytkin/rust-watchdog-add-watchdog-device-abstraction/20260813-051424
base:   https://github.com/Rust-for-Linux/linux rust-next
patch link:    https://lore.kernel.org/r/20260723161529.23759-4-iprintercanon%40gmail.com
patch subject: [PATCH v2 3/3] watchdog: softdog_rs: add Rust software watchdog driver
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260817/202608170957.oeQwdAP3-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/20260817/202608170957.oeQwdAP3-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/202608170957.oeQwdAP3-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> warning: this `impl` can be derived
   --> rust/kernel/watchdog.rs:164:1
   |
   164 | / impl Default for Options {
   165 | |     fn default() -> Self {
   166 | |         Self {
   167 | |             timeout: 0,
   ...   |
   175 | | }
   | |_^
   |
   = help: for further information visit https://rust-lang.github.io/rust-clippy/rust-1.96.0/index.html#derivable_impls
   = note: `-W clippy::derivable-impls` implied by `-W clippy::all`
   = help: to override `-W clippy::all` add `#[allow(clippy::derivable_impls)]`
   help: replace the manual implementation with a derive attribute
   |
   147 + #[derive(Default)]
   148 | pub struct Options {
   |
--
>> warning: unresolved link to `super::Info::new`
   --> rust/kernel/watchdog.rs:98:7
   |
   98 | /// [`super::Info::new`].
   |       ^^^^^^^^^^^^^^^^ no item named `Info` in module `kernel`
   |
   = note: `#[warn(rustdoc::broken_intra_doc_links)]` on by default
--
>> warning: public documentation for `Registration` links to private item `Inner`
   --> rust/kernel/watchdog.rs:392:34
   |
   392 | /// - `inner` points at a live [`Inner`] obtained from [`KBox::into_raw`],
   |                                  ^^^^^ this item is private
   |
   = note: this link will resolve properly if you pass `--document-private-items`
   = note: `#[warn(rustdoc::private_intra_doc_links)]` on by default
--
>> warning: public documentation for `Registration` links to private item `Inner`
   --> rust/kernel/watchdog.rs:395:45
   |
   395 | ///   the `ops` and `data` fields of that [`Inner`].
   |                                             ^^^^^ this item is private
   |
   = note: this link will resolve properly if you pass `--document-private-items`

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

      reply	other threads:[~2026-08-17  7:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 16:15 [PATCH v2 0/3] rust: add watchdog abstraction and Rust softdog driver Artem Lytkin
2026-07-23 16:15 ` [PATCH v2 1/3] rust: watchdog: add watchdog device abstraction Artem Lytkin
2026-07-23 16:15 ` [PATCH v2 2/3] rust: reboot: add emergency_restart() wrapper Artem Lytkin
2026-07-23 16:15 ` [PATCH v2 3/3] watchdog: softdog_rs: add Rust software watchdog driver Artem Lytkin
2026-08-17  7:43   ` kernel test robot [this message]

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=202608170957.oeQwdAP3-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=dakr@kernel.org \
    --cc=iprintercanon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lossin@kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=wim@linux-watchdog.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