mmc_wait_for_cmd(9)

📦 version 7.3.1, in nixpkgs unstable

💖 mmc_wait_for_cmd(9) 💖

okay so bestie, this is a page straight out of the Kernel API Manual (yes, the kernel has a manual, and yes it's iconic) and today's main character is mmc_wait_for_cmd. she starts a command and then waits for it to finish. patient queen behavior. 👑

✨ NAME ✨

mmc_wait_for_cmd — start a command and wait for completion 🎀

🌸 SYNOPSIS 🌸

int mmc_wait_for_cmd (struct mmc_host *host , struct mmc_command *cmd ,
int retries );

literally that's the whole signature, no cap. 🫶

🦋 ARGUMENTS 🦋

  • host — the MMC host you're starting the command on. the venue, if you will. 🏟️
  • cmd — the MMC command itself. the star of the show. ⭐
  • retries — the maximum number of retries. how many chances you're willing to give it before you're like "ok bestie, that's enough." 🙈

💜 DESCRIPTION 💜

Start a new MMC command for a host, and wait for the command to complete. that's it, that's the vibe. 💅

Return any error that occurred while the command was executing. so if it flopped, you will hear about it. 😭

Do not attempt to parse the response. ok this is the important part — do NOT go poking at the response, that's not your job here. this function is not giving "analyze the results" energy, it's giving "did it finish, yes or no" energy. stay in your lane, respectfully. 🚫🔍

🌈 SEE ALSO 🌈

Kernel file ./drivers/mmc/core/core.c, plus the whole friend group:

and that's the page!! 🧚💖 this little cutie lives in ./drivers/mmc/core and the version we're stanning is from October 2026. go forth and wait for your commands, bestie — patiently, and without parsing the response. periodt. 🍓✨

📦 where this page comes from