From: kernel test robot <lkp@intel.com>
To: Vitaly Wool <vitaly.wool@konsulko.se>, linux-mm@kvack.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Uladzislau Rezki <urezki@gmail.com>,
Danilo Krummrich <dakr@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
rust-for-linux@vger.kernel.org,
Vitaly Wool <vitaly.wool@konsulko.se>
Subject: Re: [PATCH v10 3/4] rust: add support for NUMA ids in allocations
Date: Sun, 6 Jul 2025 23:18:56 +0800 [thread overview]
Message-ID: <202507062327.TsP3JVhL-lkp@intel.com> (raw)
In-Reply-To: <20250702160910.3610134-1-vitaly.wool@konsulko.se>
Hi Vitaly,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on rust/rust-next linus/master v6.16-rc4 next-20250704]
[cannot apply to vbabka-slab/for-next]
[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/Vitaly-Wool/mm-vmalloc-allow-to-set-node-and-align-in-vrealloc/20250703-001116
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20250702160910.3610134-1-vitaly.wool%40konsulko.se
patch subject: [PATCH v10 3/4] rust: add support for NUMA ids in allocations
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250706/202507062327.TsP3JVhL-lkp@intel.com/config)
compiler: clang version 20.1.7 (https://github.com/llvm/llvm-project 6146a88f60492b520a36f8f8f3231e15f3cc6082)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250706/202507062327.TsP3JVhL-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/202507062327.TsP3JVhL-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> warning: missing documentation for an associated constant
--> rust/kernel/alloc.rs:139:5
|
139 | pub const NO_NODE: NumaNode = NumaNode(bindings::NUMA_NO_NODE);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= 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:[~2025-07-06 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 16:07 [PATCH v10 0/4] support large align and nid in Rust allocators Vitaly Wool
2025-07-02 16:08 ` [PATCH v10 1/4] mm/vmalloc: allow to set node and align in vrealloc Vitaly Wool
2025-07-04 10:10 ` Uladzislau Rezki
2025-07-02 16:08 ` [PATCH v10 2/4] mm/slub: allow to set node and align in k[v]realloc Vitaly Wool
2025-07-02 16:09 ` [PATCH v10 3/4] rust: add support for NUMA ids in allocations Vitaly Wool
2025-07-04 15:23 ` Danilo Krummrich
2025-07-05 7:17 ` Vitaly Wool
2025-07-07 7:25 ` Alice Ryhl
2025-07-06 15:18 ` kernel test robot [this message]
2025-07-02 16:09 ` [PATCH v10 4/4] rust: support large alignments " Vitaly Wool
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=202507062327.TsP3JVhL-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=urezki@gmail.com \
--cc=vitaly.wool@konsulko.se \
/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.