From: kernel test robot <lkp@intel.com>
To: Joel Fernandes <joelagnelf@nvidia.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC v5 3/6] rust: gpu: Add GPU buddy allocator bindings
Date: Tue, 23 Dec 2025 15:45:31 +0800 [thread overview]
Message-ID: <202512232015.WVmaP40F-lkp@intel.com> (raw)
In-Reply-To: <20251219203805.1246586-4-joelagnelf@nvidia.com>
Hi Joel,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on linus/master v6.19-rc2 next-20251219]
[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/Joel-Fernandes/rust-clist-Add-support-to-interface-with-C-linked-lists/20251220-044108
base: https://gitlab.freedesktop.org/drm/misc/kernel.git drm-misc-next
patch link: https://lore.kernel.org/r/20251219203805.1246586-4-joelagnelf%40nvidia.com
patch subject: [PATCH RFC v5 3/6] rust: gpu: Add GPU buddy allocator bindings
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20251223/202512232015.WVmaP40F-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/20251223/202512232015.WVmaP40F-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/202512232015.WVmaP40F-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0425]: cannot find function `gpu_buddy_block_offset` in crate `bindings`
--> rust/kernel/gpu/buddy.rs:474:28
|
474 | unsafe { bindings::gpu_buddy_block_offset(self.as_raw()) }
| ^^^^^^^^^^^^^^^^^^^^^^ help: a function with a similar name exists: `gpu_buddy_block_print`
|
::: rust/bindings/bindings_generated.rs:61566:5
|
61566 | pub fn gpu_buddy_block_print(mm: *mut gpu_buddy, block: *mut gpu_buddy_block);
| ------------------------------------------------------------------------------ similarly named function `gpu_buddy_block_print` defined here
--
>> error[E0425]: cannot find function `gpu_buddy_block_order` in crate `bindings`
--> rust/kernel/gpu/buddy.rs:480:28
|
480 | unsafe { bindings::gpu_buddy_block_order(self.as_raw()) }
| ^^^^^^^^^^^^^^^^^^^^^ help: a function with a similar name exists: `gpu_buddy_block_print`
|
::: rust/bindings/bindings_generated.rs:61566:5
|
61566 | pub fn gpu_buddy_block_print(mm: *mut gpu_buddy, block: *mut gpu_buddy_block);
| ------------------------------------------------------------------------------ similarly named function `gpu_buddy_block_print` defined here
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-12-23 7:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 20:37 [PATCH RFC v5 0/6] nova-core: Memory management initial patches Joel Fernandes
2025-12-19 20:37 ` Joel Fernandes
2025-12-19 20:38 ` [PATCH RFC v5 1/6] rust: clist: Add support to interface with C linked lists Joel Fernandes
2025-12-19 20:38 ` Joel Fernandes
2025-12-19 20:38 ` [PATCH RFC v5 2/6] gpu: Move DRM buddy allocator one level up Joel Fernandes
2025-12-19 20:38 ` Joel Fernandes
2025-12-19 20:38 ` [PATCH RFC v5 3/6] rust: gpu: Add GPU buddy allocator bindings Joel Fernandes
2025-12-19 20:38 ` Joel Fernandes
2025-12-20 20:39 ` kernel test robot
2025-12-23 7:45 ` kernel test robot [this message]
2025-12-19 20:38 ` [PATCH RFC v5 4/6] nova-core: mm: Add support to use PRAMIN windows to write to VRAM Joel Fernandes
2025-12-19 20:38 ` Joel Fernandes
2025-12-19 20:38 ` [PATCH RFC v5 5/6] docs: gpu: nova-core: Document the PRAMIN aperture mechanism Joel Fernandes
2025-12-19 20:38 ` Joel Fernandes
2025-12-19 20:38 ` [PATCH RFC v5 6/6] nova-core: Add PRAMIN aperture self-tests Joel Fernandes
2025-12-19 20:38 ` Joel Fernandes
2025-12-19 22:39 ` ✓ i915.CI.BAT: success for nova-core: Memory management initial patches Patchwork
2025-12-22 14:15 ` ✗ CI.checkpatch: warning " Patchwork
2025-12-22 14:17 ` ✓ CI.KUnit: success " Patchwork
2025-12-22 14:32 ` ✗ CI.checksparse: warning " Patchwork
2025-12-22 14:53 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-12-22 15:50 ` ✓ Xe.CI.Full: success " Patchwork
2025-12-23 5:47 ` ✗ i915.CI.Full: failure " Patchwork
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=202512232015.WVmaP40F-lkp@intel.com \
--to=lkp@intel.com \
--cc=joelagnelf@nvidia.com \
--cc=llvm@lists.linux.dev \
--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.