rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Filipe Xavier" <felipeaggger@gmail.com>,
	"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>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, daniel.almeida@collabora.com,
	rust-for-linux@vger.kernel.org, felipe_life@live.com,
	linux-kernel@vger.kernel.org,
	Filipe Xavier <felipeaggger@gmail.com>,
	Lyude Paul <lyude@redhat.com>
Subject: Re: [PATCH v2] rust: add new macro for common bitmap operations
Date: Thu, 27 Mar 2025 13:05:48 +0800	[thread overview]
Message-ID: <202503271256.KMMeri1M-lkp@intel.com> (raw)
In-Reply-To: <20250325-feat-add-bitmask-macro-v2-1-d3beabdad90f@gmail.com>

Hi Filipe,

kernel test robot noticed the following build warnings:

[auto build test WARNING on beeb78d46249cab8b2b8359a2ce8fa5376b5ad2d]

url:    https://github.com/intel-lab-lkp/linux/commits/Filipe-Xavier/rust-add-new-macro-for-common-bitmap-operations/20250325-213139
base:   beeb78d46249cab8b2b8359a2ce8fa5376b5ad2d
patch link:    https://lore.kernel.org/r/20250325-feat-add-bitmask-macro-v2-1-d3beabdad90f%40gmail.com
patch subject: [PATCH v2] rust: add new macro for common bitmap operations
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250327/202503271256.KMMeri1M-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
rustc: rustc 1.78.0 (9b00956e5 2024-04-29)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250327/202503271256.KMMeri1M-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/202503271256.KMMeri1M-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> warning: unresolved link to `BitOr`
   --> rust/kernel/impl_flags.rs:8:55
   |
   8 | /// - Implementations of common bitmask operations ([`BitOr`], [`BitAnd`], etc.).
   |                                                       ^^^^^ no item named `BitOr` 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 `BitAnd`
   --> rust/kernel/impl_flags.rs:8:66
   |
   8 | /// - Implementations of common bitmask operations ([`BitOr`], [`BitAnd`], etc.).
   |                                                                  ^^^^^^ no item named `BitAnd` in scope
   |
   = help: to escape `[` and `]` characters, add '' before them like `[` or `]`

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

  parent reply	other threads:[~2025-03-27  5:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 13:10 [PATCH v2] rust: add new macro for common bitmap operations Filipe Xavier
2025-03-25 13:34 ` Benno Lossin
2025-03-25 14:17   ` Miguel Ojeda
2025-03-25 13:54 ` Daniel Almeida
2025-03-27  5:05 ` kernel test robot [this message]
2025-03-31 22:29 ` Lyude Paul
2025-03-31 22:35   ` Daniel Almeida
2025-03-31 22:50     ` Lyude Paul

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=202503271256.KMMeri1M-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=felipe_life@live.com \
    --cc=felipeaggger@gmail.com \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lyude@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    /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;
as well as URLs for NNTP newsgroup(s).