rdma_device_to_drv_device(9)

📦 version 7.3.1, in nixpkgs unstable

💅 rdma_device_to_drv_device(9) — a Kernel API Manual moment ✨

okay so bestie, welcome to the Kernel API Manual page for rdma_device_to_drv_device, and honestly? it's giving "small but mighty." 🎀

🌸 NAME 🌸

rdma_device_to_drv_device — it's a helper macro that lets you reach back to the driver's ib_device holder structure starting from a device pointer. like, you got a dev, you wanna find your way home to the driver struct? that's the whole vibe. 🫶

✨ SYNOPSIS ✨

rdma_device_to_drv_device (dev , drv_dev_struct , ibdev_member );

🦋 ARGUMENTS 🦋

okay so the manpage is being lowkey mysterious here — all three args are literally marked as -- undescribed -- in the source. not me making things up, that's genuinely what it says 😭

  • dev — -- undescribed --
  • drv_dev_struct — -- undescribed --
  • ibdev_member — -- undescribed --
🙈 yes bestie, all three of them. i'm not gonna invent lore for arguments the page refuses to describe. we respect the source.

💀 NOTE 💀

okay this is the important part, so read it twice, fr fr:

New drivers should not make use of this API. 🚩

This API is only for existing drivers who have exposed sysfs entries using ops->device_group.

so if you're writing a fresh driver and you're eyeing this macro like "omg cute, i want that"? nope. not for you, newbie. it's legacy-adjacent — a little bit of a relic, and it's staying exactly in its lane. periodt. 👑

🌈 SEE ALSO 🌈

the cross-reference section goes hard, ngl. it's a whole friend group:

like i said. huge friend group. 💜

that's the whole page, bestie — short, a little cryptic on the arguments, and very clear about who shouldn't be using it. slay. 💅✨

and for the credits moment 🎬: this one lives over in ./include/rdma, stamped October 2026. mwah. 🍓

📦 where this page comes from