do_passive_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… do_passive_init(9) β€” the Kernel API Manual ✨

okay so bestie, welcome to the do_passive_init(9) page, from the Kernel API Manual, no big deal, just a little function that finishes the probe when your partner finally decides to show up 🫢


🌸 NAME 🌸

do_passive_init β€” literally the glow-up that completes probing once the partner device is detected πŸ’–


✨ SYNOPSIS ✨

int do_passive_init (struct ibmvnic_adapter *adapter );

πŸŽ€ ARGUMENTS πŸŽ€

  • adapter β€” the ibmvnic_adapter struct, aka the main character of this whole situation πŸ‘‘

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so picture this: the ibmvnic device boots up and there's no partner device to communicate with 😭 the vibes are off, the partner just isn't there. but then β€” plot twist β€” that partner device comes online at a later time 🌈 and that's when this function gets called, to complete the initialization process of the ibmvnic device. slay. it's giving "finishing what we started" energy fr fr πŸ’…

ngl, the caller is expected to hold rtnl_lock πŸ”’ so like… do that. it's not optional, bestie.

so what does it return? okay:

  • returns non-zero if sub-CRQs aren't initialized properly β€” and that leaves the device in the down state πŸ’€ not iconic, but that's the deal
  • returns 0 upon success, and the device is in the PROBED state πŸ‘‘ periodt

🧚 SEE ALSO 🧚


and that's the whole page, bestie, you ate that πŸ’– this icon lives over in ./drivers/net/ethernet/ibm and it's stamped October 2026 ⭐ go forth and complete those probes, iykyk πŸ¦‹πŸŽ€

πŸ“¦ where this page comes from