nfp_cpp_explicit_put(9)

📦 version 7.3.1, in nixpkgs unstable

💅 nfp_cpp_explicit_put — the kernel API manual, bestie edition ✨

okay so this is nfp_cpp_explicit_put(9) from the Kernel API Manual, and honestly? she's a little function with one job and she does it. sit down, grab a strawberry 🍓, let's get into it.

🌸 NAME 🌸

nfp_cpp_explicit_put — setting up the write (pull) data for an explicit access, that's the whole vibe 💫

🎀 SYNOPSIS 🎀

int nfp_cpp_explicit_put (struct nfp_cpp_explicit *expl , const void
*buff , size_t len );

like, that's her signature. iconic. no notes. 👑

🦋 ARGUMENTS 🦋

  • expl — the NFP CPP Explicit handle 💜 this is your girl, she's the one you're operating on
  • buff — the data you want the target to pull in during the transaction 🫶 it's literally the payload
  • len — length of data, in bytes. just bytes. that's it. that's the number 📏

✨ DESCRIPTION ✨

okay so here's the tea ☕ — the len parameter must be less than or equal to 128 bytes. not 129. not "roughly 128". <= 128. periodt. 💅

and listen, there's a little gotcha 👀 — if you call this function before the configuration registers are set, it will return -EINVAL. so like… set your config registers first, bestie. do the steps in order. main character energy means reading the docs first 😭

🔥 RETURN 🔥

0, or -ERRNO — that's it, that's the whole return section. slay. 🌈

👑 SEE ALSO 👑

buckle up buttercup, this list is LONG and we are NOT skipping a single one, because every single one of these deserves her moment 💖

like… forty-seven references. she said "link everything or nothing at all" and honestly? respect. 🙈💀

quick reminder bestie: len <= 128 bytes, and config registers go FIRST or you get -EINVAL. no cap. 🧚

and that's the page!! this absolute baddie of a manpage comes from the kernel source at ./drivers/net/ethernet/netrono... and it's dated October 2026 — so yeah, she's from the future, she's serving, and she's the Kernel API Manual's finest. bye bestie, go write some pull data 💅✨🎀🦋🌸💖

📦 where this page comes from