fm10k_tlv_attr_put_value(9)

📦 version 7.3.1, in nixpkgs unstable

✨ fm10k_tlv_attr_put_value ✨

Okay bestie, welcome to the fm10k_tlv_attr_put_value page — it's a section 9 Kernel API Manual situation, and honestly it's giving "tiny function, big responsibility" energy. Let me put you on. 🫶

🌸 NAME 🌸

fm10k_tlv_attr_put_value — store an integer value attribute in a message. That's it, that's the whole vibe. 💅

🦋 SYNOPSIS 🦋

s32 fm10k_tlv_attr_put_value (u32 *msg , u16 attr_id , s64 value , u32
len );

Like, that's the exact signature, character for character, no notes. 🔥

🎀 ARGUMENTS 🎀

  • msg — pointer to the message block. It's the canvas, the main character of this whole operation. 🖼️
  • attr_id — the attribute ID, aka which attribute you're targeting. iykyk.
  • value — the value to be written. This is the actual star of the show. ⭐
  • len — size of the value. Spoiler: it's gotta be one of the blessed sizes, more on that below. 👀

💖 DESCRIPTION 💖

So here's the tea: this function places an integer value of up to 8 bytes in size into a message attribute. Up to 8 bytes. Like, that's the ceiling, don't push it. 😭

And the function will return success provided that:

  • msg is a valid pointer, and
  • len is 1, 2, 4, or 8.

That's it. Those are the four iconic numbers. 1, 2, 4, 8 — no cap, no in-between sizes, periodt. ✨

👑 SEE ALSO 👑

First up, the kernel file this whole thing lives in:

./drivers/net/ethernet/intel/fm10k/fm10k_tlv.c

And now the whole friend group — every single one of them, bestie, I'm not skipping anybody: 🧚

Genuinely obsessed with how many of these there are. Go read them all, they ate. 💜

And that's the page, bestie! 🌈 A lil sign-off moment for the fine print: this beauty is sourced from ./drivers/net/ethernet/intel/f... and dated October 2026, and it's fm10k_tlv_attr_put_value(9) all the way down. Slay. 💅💖

📦 where this page comes from