_base_deter...on_discovery(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, welcome to the Kernel API Manual, and today's main character is the page _base_deter...on_discovery(9) and its function _base_determine_wait_on_discovery — and yes, the one-liner is literally desposition 🫶 (that's the manual's word, not mine, we don't gatekeep spelling here, we respect the source 💅).

✨ SYNOPSIS ✨

int _base_determine_wait_on_discovery (struct MPT3SAS_ADAPTER *ioc );

🎀 ARGUMENTS 🎀

  • ioc — the per adapter object. that's it, that's the whole vibe check. one (1) argument, living its best life 💖

🦋 DESCRIPTION 🦋

bestie it's literally in the name: this function decides whether to wait on discovery to complete. that's the whole personality ✨

and why would you wait, you ask? because it's used to either locate the boot device, or to report volumes ahead of physical devices. iconic ordering behaviour, no cap 👑

🌈 RETURN 🌈

  • 1 — for wait 🕐 (yes bestie, we're waiting)
  • 0 — for don't wait 🏃‍♀️ (we move, periodt)

👑 SEE ALSO 👑

okay so this is the part where the page absolutely ate — like, look at this list, it's giving "tagged everyone in the group chat" energy 😭💀 but every single one of these is a real reference, so here we go, in the exact order, fr fr:

also the kernel file itself lives at ./drivers/scsi/mpt3sas/mpt3sas_base.c — that's the source of truth, go read it, iykyk 🔥

ngl bestie, that SEE ALSO list is a whole mood board of the mpt3sas base layer. every name here is exactly as it appears in the manual — no edits, no merges, we don't do that here 💅

and that's the page!! 🫶 this lil delivery came from the source tree at ./drivers/scsi/mpt3sas, dated October 2026 — so go forth, know whether to wait, and slay ✨🎀🦋

📦 where this page comes from