ice_adapter_get(9)

💖 ice_adapter_get — bestie edition 💖

okay so this is ice_adapter_get(9) from the Kernel API Manual, and honestly? it's a little baddie of a function that just hands you a pointer to a shared thing. let's get into it 🫶

---

✨ NAME ✨

ice_adapter_get — literally just: get a shared ice_adapter structure. that's the whole vibe. 🎀

---

🌸 SYNOPSIS 🌸

struct ice_adapter * ice_adapter_get (struct pci_dev *pdev );

---

🦋 ARGUMENTS 🦋

• pdev — pointer to the pci_dev whose driver is the one getting the ice_adapter. it's giving "hey bestie, which device are you?" energy 💅

---

👑 DESCRIPTION 👑

so what does it actually do? it gets you a pointer to a shared ice_adapter structure. no cap, that's it.

here's the tea though: Physical functions (PFs) of the same multi-function PCI device all share one ice_adapter structure. one adapter, many PFs, all vibing together ✨

and because sharing means caring, the ice_adapter is reference-counted. that means the PF driver must use ice_adapter_put to release its reference. like, you grab it, you put it back. periodt. 🔥

not releasing your reference with ice_adapter_put is not the move, bestie — that reference count is not gonna untangle itself 😭

---

🧚 CONTEXT 🧚

Process, may sleep. so it's a chill, sleepable context — no need to panic about atomics here 💜

---

⭐ RETURN ⭐

• on success — pointer to ice_adapter. iconic. we love to see it 🌈
• on error — ERR_PTR. and the only possible error is -ENOMEM. that's the entire error menu, fr fr 💀

---

🍓 SEE ALSO 🍓

• Kernel file ./drivers/net/ethernet/intel/ice/ice_adapter.c — go read the source, iykyk 👀
• ice_adapter_put(9) — the partner in crime, the other half of the refcount story 🫶

---

and that's the whole page, bestie — no notes, ate and left no crumbs 💖✨

sign-off szn: this one lives under ./drivers/net/ethernet/intel/ice, dated October 2026, and it's the ice_adapter_get(9) page — mwah 💋🎀