mpi3mr_devinfochg_evt_bh(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

mpi3mr_devinfochg_evt_bh β€” the DeviceInfoChange evt bottomhalf, bestie. that's it, that's the whole vibe πŸ¦‹

okay so real talk, we're deep in the kernel API manual rn (yes, the Kernel API Manual, she's fancy), and this function is the one that handles the bottom half of a Device Info Change event. lowkey iconic.


✨ SYNOPSIS ✨

void mpi3mr_devinfochg_evt_bh (struct mpi3mr_ioc *mrioc , struct mpi3_device_page0 *dev_pg0 );

πŸŽ€ ARGUMENTS πŸŽ€

  • mrioc β€” the adapter instance reference, aka the lil handle to the controller we're talking about 🫢
  • dev_pg0 β€” the new device page0. like, the fresh tea on this device πŸ‘‘

🌸 DESCRIPTION 🌸

so what does she actually do? she processes the Device Info Change event, and then β€” based on the device's new information β€” she does one of three things:

  1. exposes the device to the upper layers,
  2. removes the device from the upper layers,
  3. or updates the details of the device.

that's it! no cap, three possible outcomes, all dependent on whatever new info the device is serving ✨


πŸ’€ RETURN πŸ’€

Nothing. literally nothing. void-coded, she gives you zero back 😭 (not everything has to return something, periodt)


πŸ‘‘ SEE ALSO πŸ‘‘

buckle up bestie, this list is long β€” but every single one of these is part of the family, so show some respect πŸ’–


anyway that's the page, bestie πŸ’– this one lives under ./drivers/scsi/mpi3mr, and she's dated October 2026 β€” so yeah, future girl summer 🌈. go read the source, ily, bye 🫢✨

πŸ“¦ where this page comes from