nfp_nfdk_rx_csum_has_errors(9)

💅 nfp_nfdk_rx_csum_has_errors(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ — this lil page is all about nfp_nfdk_rx_csum_has_errors, which is genuinely the group-chat friend who does the vibe check on your RX descriptors and tells you if literally any of them are giving checksum-error energy 😭💀

---

🌸 NAME 🌸

nfp_nfdk_rx_csum_has_errors — the group check that asks "does this rxd have any csum errors?" 🫶 No cap, that's the whole job. It's the "hey bestie, is something wrong in here" function of the NFP NFDK datapath 👑

---

✨ SYNOPSIS ✨

int nfp_nfdk_rx_csum_has_errors (u16 flags );

That's it. One little arg, one little int back. Lowkey iconic in its simplicity 💖

---

🎀 ARGUMENTS 🎀

• flags — the RX descriptor flags field, and heads up, it's in CPU byte order 🧠✨ (not little-endian-or-whatever energy, just your CPU's native vibe, iykyk)

---

🦋 SEE ALSO 🦋

Sibling functions, the whole squad, go check 'em out 💜

• Kernel file ./drivers/net/ethernet/netronome/nfp/nfdk/dp.c 📁
• nfp_nfdk_tx(9)
• nfp_nfdk_tx_complete(9)
• nfp_nfdk_rx_give_one(9)
• nfp_nfdk_rx_ring_fill_freelist(9)
• nfp_nfdk_rx_csum(9)
• nfp_nfdk_rx(9)
• nfp_nfdk_poll(9)

---

bestie real talk: this page keeps every detail exactly as it was, so don't go renaming flags or reordering the byte order or anything 🙈 — the facts stay facts, only the vibe got a glow-up 💅

okay that's the whole page, mwah 💋 — sourced straight from ./drivers/net/ethernet/netrono... and dated October 2026, so mark your calendars, main character energy only 🌈⭐👑