_scsih_is_nv...escsi_device(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

okay bestie, gather round — this is _scsih_is_nvme_pciescsi_device, and yes, the manual page is literally titled _scsih_is_nv...escsi_device(9) because somebody let the truncation gremlin cook. it's from the Kernel API Manual, and it does exactly one job: it determines if device is an pcie nvme/scsi device. that's it. that's the whole personality. 🎀

✨ SYNOPSIS ✨

int _scsih_is_nvme_pciescsi_device (u32 device_info );

it's giving "one argument, one int, no drama." no cap. 🦋

🫶 ARGUMENTS 🫶

  • device_info — a bitfield providing information about the device. that's the whole snack. that's all you're handing it.

🌸 CONTEXT 🌸

none

literally none. zero context needed. it's a free agent, it answers to nobody. main character energy but make it stateless. 💀

🔥 DESCRIPTION 🔥

Returns 1 if device is pcie device type nvme/scsi.

that's the entire bit. one means yes, this thing is pcie and it's nvme or it's scsi. iykyk. not me being obsessed with a single return value but here we are 💖

👑 SEE ALSO 👑

so first up, the kernel file this whole situation lives in:

Kernel file ./drivers/scsi/mpt3sas/mpt3sas_scsih.c

and then — bestie, take a breath, hydrate, stretch, because this list is LONG and i refuse to skip a single one of these icons 👑✨

like. i told you. LONG. but we got through it together and honestly that's growth 💜🧚

ok real talk — nothing here is deprecated or dangerous, it's literally a one-line helper that tells you "yes bestie, pcie nvme/scsi" or not. no landmines, no caveats, we're chilling 🍓

and that's the whole page, bestie! this lil beauty ships out of ./drivers/scsi/mpt3sas and is dated October 2026 — so go forth, check your device types, and remember: one bitfield in, one int out, slay 💅✨🌈

📦 where this page comes from