mpi3mr_scan_finished(9)

📦 version 7.3.1, in nixpkgs unstable

💖 mpi3mr_scan_finished(9) — Kernel API Manual 💖

okay so bestie, welcome to the <pink>mpi3mr_scan_finished</pink> page, straight out of the Kernel API Manual. it's a tiny little callback with a big job and honestly it's giving main character energy in the SCSI scan pipeline. let's get into it 🎀

✨ NAME ✨

mpi3mr_scan_finished — the scan finished callback handler, aka the "are we done yet??" bouncer 🕵️‍♀️

🌸 SYNOPSIS 🌸

int mpi3mr_scan_finished (struct Scsi_Host *shost , unsigned long time );

🦋 ARGUMENTS 🦋

  • shost — a reference to the SCSI host. like, the actual host object, bestie, not a copy, not a vibe — the reference.
  • time — the jiffies counted from the scan start. ⏱️ that's your "how long has this been going" clock.

💅 DESCRIPTION 💅

so what does it actually do? it checks whether the port enable is completed, timedout, or failed — those are the three moods — and then it sets the scan status accordingly. and if any recovery is required? it does that too before setting the status. no cap, it's out here doing recovery on the side like it's nothing 🫶

tl;dr: it's the callback that checks the port enable outcome and reports back whether the party's over.

👑 RETURN 👑

  • 1 — scan finished or timed out. the ride is over, get off 🎢
  • 0 — still in progress. hold please, we're not there yet 😭

🌈 SEE ALSO 🌈

the kernel file lives right here, bestie:

  • ./drivers/scsi/mpi3mr/mpi3mr_os.c

and now the friend group — everybody the driver hangs out with:

and that's the whole page, bestie 🧚 it lives under ./drivers/scsi/mpi3mr, dated October 2026 — so go forth, check your port enable status, and slay 💜

📦 where this page comes from