From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12-2026-06 7/7] warning: redundant explicit link target
Date: Thu, 15 Oct 2026 02:21:05 +0200 [thread overview]
Message-ID: <202610150221.Uae1ZMN6-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android16-6.12-2026-06
head: d463a34c5b280147355726f1188b49064527fa9c
commit: acbdc23728b15c406133ca2e2cfe90ba377d61da [7/7] BACKPORT: FROMGIT: rust: sync: add const constructor for raw_spinlock_t
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20261015/202610150221.Uae1ZMN6-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/20261015/202610150221.Uae1ZMN6-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/202610150221.Uae1ZMN6-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> warning: redundant explicit link target
--> rust/kernel/sync/lock/spinlock.rs:29:40
|
29 | /// instances is with the [`pin_init`](crate::pin_init) and [`new_spinlock`] macros.
| ---------- ^^^^^^^^^^^^^^^ explicit target is redundant
| |
| because label contains path that resolves to same destination
|
= note: when a link's destination is not specified,
the label is used to resolve intra-doc links
= note: `#[warn(rustdoc::redundant_explicit_links)]` on by default
help: remove explicit link target
|
29 - /// instances is with the [`pin_init`](crate::pin_init) and [`new_spinlock`] macros.
29 + /// instances is with the [`pin_init`] and [`new_spinlock`] macros.
|
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-15 0:21 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=202610150221.Uae1ZMN6-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.