PANTHOR_UOBJ...IZE_INTERNAL(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– PANTHOR_UOBJ_MIN_SIZE_INTERNAL(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for PANTHOR_UOBJ_MIN_SIZE_INTERNAL(9) β€” the header/footer abbreviate it as PANTHOR_UOBJ...IZE_INTERNAL(9), which is giving β€œmy name got cut off in the group chat” energy 😭. This one is all about getting the minimum user object size, and it's lowkey internal. Let's go. πŸ’…

🌸 NAME 🌸

  • PANTHOR_UOBJ_MIN_SIZE_INTERNAL β€” Get the minimum user object size πŸ’–

✨ SYNOPSIS ✨

Here's the call, bestie β€” keep it exactly like this:

PANTHOR_UOBJ_MIN_SIZE_INTERNAL (_typename , _last_mandatory_field );

🧾 ARGUMENTS 🧾

  • _typename β€” Object type. 🫢
  • _last_mandatory_field β€” Last mandatory field. πŸŽ€

πŸ› οΈ DESCRIPTION πŸ› οΈ

Okay so the whole point: get the minimum user object size based on the last mandatory field name, A.K.A, the name of the last field of the structure at the time this structure was added to the uAPI. That's the vibe. ✨

⚠️ Don't use directly! Use PANTHOR_UOBJ_DECL instead. No cap, that's literally the rule. πŸ’…

πŸ‘€ SEE ALSO πŸ‘€

Go peek at these, bestie β€” bring snacks: πŸ“


source: ./drivers/gpu/drm/panthor Β· manual: Kernel API Manual Β· date: October 2026 β€” and yes, the footer title is still PANTHOR_UOBJ...IZE_INTERNAL(9) 😭 mwah, bye bestie πŸ’‹πŸ’…βœ¨

πŸ“¦ where this page comes from