doc_get_op_status(9)

📦 version 7.3.1, in nixpkgs unstable

💅 doc_get_op_status — the kernel API manual, but make it cute

okay so bestie, this one's from the Kernel API Manual, section 9 (that's the kernel developer's section, iykyk). Let's get into it 🫶

✨ NAME ✨

doc_get_op_status — get the erase/write operation status 💖

Like, it literally just tells you where your erase/write op is at. Main character energy for a tiny function.

🌸 SYNOPSIS 🌸

int doc_get_op_status (struct docg3 *docg3 );

That's it. That's the whole vibe check. One arg, returns an int. Slay. ✨

🎀 ARGUMENTS 🎀

  • docg3 — the device 🦋 (the actual struct docg3 you're poking at, no cap)

💜 DESCRIPTION 💜

So what this does is it queries the status from the chip, and then returns it. That's genuinely the whole thing, bestie — it goes and asks the chip "hey what's up" and hands you back the answer. 😭

It returns the status, and that status comes as DOC_PLANES_STATUS_* bits. Those are the bits you're looking at, periodt. 🌈

not me writing three sentences about a function that does exactly one thing 💀 but that's the manpage, and we keep every detail here, fr fr

👑 SEE ALSO 👑

Kernel file ./drivers/mtd/devices/docg3.c — that's where the whole crew lives 🧚

And now the entire friend group, all of them, in order, no skipping (I would never 😤):

look at that list. forty-one little icons. ate and left no crumbs 🔥

and that's the page!! 🌟 this one comes from ./drivers/mtd/devices, dated October 2026, and it's doc_get_op_status(9) all the way down. mwah, go read your chip status bestie 💅💖

📦 where this page comes from