PANTHOR_UOBJ_GET_ARRAY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… PANTHOR_UOBJ_GET_ARRAY πŸ’…

okay bestie, welcome to the kernel API manual, this one's a macro from the PANTHOR_UOBJ_GET_ARRAY(9) page and it is literally the vibe of "copy that user object array into a kernel one for me bestie" 🫢


✨ NAME ✨

PANTHOR_UOBJ_GET_ARRAY β€” Copy a user object array to a kernel accessible object array. no cap, that's the whole job πŸ’–


🌸 SYNOPSIS 🌸

PANTHOR_UOBJ_GET_ARRAY (_dest_array , _uobj_array );

that's it. two args. she's lowkey minimal and iconic like that ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • _dest_array β€” Local variable that will hold the newly allocated kernel object array. like, this is where the fresh new kernel-side array lands after the copy, so make it a local and let the macro do its thing πŸŽ€
  • _uobj_array β€” The drm_panthor_obj_array object describing the user object array. yes queen, that struct is the whole map of what's coming over from userspace πŸ—ΊοΈβœ¨

πŸ‘‘ RETURN πŸ‘‘

0 on success, a negative error code otherwise. that's it, that's the whole story β€” zero means slay, negative means something went sideways and you should absolutely check it πŸ”₯


πŸ’œ SEE ALSO πŸ’œ

okay so this is the whole group chat, strap in bestie, we're listing everyone:


ngl that SEE ALSO list is giving "tagged everyone in the group project" energy πŸ’€ but every single one of them is fr fr part of the panthor story, so go read them if you're curious 🧚

okay that's the whole page, bestie!! πŸ’œ this little drop shipped out of ./drivers/gpu/drm/panthor back in October 2026, and yeah β€” it's still wearing the PANTHOR_UOBJ_GET_ARRAY(9) name tag, main character energy as always πŸ‘‘βœ¨ go copy some object arrays, love u, bye!! πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from