nfc_alloc_send_skb(9)

📦 version 7.3.1, in nixpkgs unstable

🦋 nfc_alloc_send_skb(9) 🦋

okay bestie so this is a page from the Kernel API Manual (yes, the kernel kernel, we're being fancy today ✨) and it's all about nfc_alloc_send_skb — think of it as the little function whose whole job is allocating an skb for data exchange responses. it's giving "backstage crew of the NFC world" energy, lowkey iconic 👑

🌸 NAME 🌸

nfc_alloc_send_skb — allocate an skb for data exchange responses 💖

✨ SYNOPSIS ✨

struct sk_buff * nfc_alloc_send_skb (struct nfc_dev *dev , struct sock
*sk , unsigned int flags , unsigned int size , unsigned int *err );

like, that's the whole vibe right there — it hands you back a struct sk_buff *, no cap 🫶

🎀 ARGUMENTS 🎀

  • dev — the device that's sending the response 📡 literally the main character of this operation
  • sk — the socket that's sending the response 🔌 the other half of the sending situation
  • flags — the MSG_DONTWAIT flag 🏃‍♀️ that's the one flag listed here, fr fr
  • size — the size to allocate 📏 how much room you're asking for, bestie
  • err — a pointer to memory where the error code gets stored 🫣 so like, if things go sideways, that's where you find out, iykyk
ngl, err is a pointer and you do need to give it real memory to point at — the page says "pointer to memory to store the error code", and we are not out here inventing extra lore 💅

🌈 SEE ALSO 🌈

kernel file ./net/nfc/core.c — and the whole friend group 💜:

💀 friendly reminder that this page is a stub vibe — it's got the args and the see-alsos, and that's genuinely all she wrote. no examples, no return value section, no exit statuses, nothing. so we don't hallucinate any, periodt.

and that's the whole page bestie, go forth and allocate 🌟 mwah 💋

signed off from ./net/nfc, dated October 2026 — stay slaying, kernel girlies 🎀🦋✨

📦 where this page comes from