dprc_get_container_id(9)

📦 version 7.3.1, in nixpkgs unstable

💜 dprc_get_container_id 💜

okay so bestie, welcome to the Kernel API Manual entry for dprc_get_container_id — it's a tiny little function that goes and fetches the container ID that belongs to a given portal. that's the whole vibe. short, sweet, slays, done ✨

🌸 NAME 🌸

dprc_get_container_id — literally "Get container ID associated with a given portal." that's it, that's the mission statement 🎀

✨ SYNOPSIS ✨

int dprc_get_container_id (struct fsl_mc_io *mc_io , u32 cmd_flags , int *container_id );

she takes three things and returns an int, periodt 💅

🎀 ARGUMENTS 🎀

  • mc_io — pointer to the Mc portal's I/O object. this is the portal bestie in question, the whole reason we're here 🫶
  • cmd_flags — the command flags, and the manual says it's one or more of 'MC_CMD_FLAG_'. yes that trailing underscore is doing its own thing, we don't question the source, we just report it 🧚
  • container_id — the requested container id. this is the int * you hand over so the answer has somewhere cute to live 🦋
ngl the original text for container_id is just "Requested container id" and honestly? iconic minimalism. no filler, no fluff, just vibes.

🦋 RETURN 🦋

so… this section exists in the manual, but it is empty. like, genuinely blank. the manpage does not describe the return value here, and i'm not about to make one up for you, bestie — that would be a lie and lying about kernel APIs is not the move 💀

so: the function returns int per the synopsis, and the RETURN section gives you zero further detail. the way that the docs just said "figure it out" 😭

💜 SEE ALSO 💜

the kernel file lives at ./drivers/bus/fsl-mc/dprc.c, and if you want the whole friend group, here's everyone:

and that's the page! 🎉 this little gem comes to you from ./drivers/bus/fsl-mc, dated October 2026 — go read the neighbors, stay hydrated, and may your container IDs always be the one you asked for 🌈💖

📦 where this page comes from