nfc_vendor_c...oc_reply_skb(9)

💖 nfc_vendor_cmd_alloc_reply_skb 💖

🎀 NAME 🎀

okay so this page is from the Kernel API Manual, and it is literally about allocating a vendor command reply. bestie, the function is nfc_vendor_cmd_alloc_reply_skb, and its whole name-brand vibe is: allocate vendor command reply. ✨

🌸 SYNOPSIS 🌸

struct sk_buff * nfc_vendor_cmd_alloc_reply_skb (struct nfc_dev *dev ,
u32 oui , u32 subcmd , int approxlen );

🦋 ARGUMENTS 🦋

• dev — the nfc device.
• oui — the vendor oui.
• subcmd — -- undescribed -- 😭 the original manpage literally says that, so that's all we have.
• approxlen — an upper bound of the length of the data that will be put into the skb.

💅 DESCRIPTION 💅

This function allocates and pre-fills an skb for a reply to a vendor command. It is intended for a reply, so calling it outside of a vendor command's doit operation is invalid. no cap, do not do that. 💀

The returned skb is pre-filled with some identifying data in a way that any data that is put into the skb (with skb_put, nla_put or similar) will end up being within the NFC_ATTR_VENDOR_DATA attribute. So all that needs to be done with the skb is adding data for the corresponding userspace tool, which can then read that data out of the vendor data attribute. You must not modify the skb in any other way. periodt. 🫶

When done, call nfc_vendor_cmd_reply with the skb and return its error code as the result of the doit operation.

⚠️ reminder bestie: this is for replies inside a vendor command's doit operation. anywhere else is invalid. 🔥

⭐ RETURN ⭐

An allocated and pre-filled skb. NULL if any errors happen. that's the whole return vibe. 💛

🌈 SEE ALSO 🌈

• Kernel file ./include/net/nfc/nfc.h
• struct nfc_target(9)
• nfc_free_device(9)
• nfc_set_parent_dev(9)
• nfc_set_drvdata(9)
• nfc_get_drvdata(9)
• nfc_device_name(9)

signing off from source/version land: ./include/net/nfc 💖 dated October 2026 — footer page name is nfc_vendor_c...oc_reply_skb(9). byeee bestie 🫶✨