qed_mcp_read_ufp_config(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– qed_mcp_read_ufp_config β€” a Kernel API Manual moment πŸ’–

Okay so bestie, welcome to the Kernel API Manual (yes that's the manual name, we're fancy here ✨) and today's main character is qed_mcp_read_ufp_config(9). The whole entire job? Read ufp config from the shared memory. That's the vibe. That's the plot. πŸŽ€


✨ NAME ✨

qed_mcp_read_ufp_config β€” Read ufp config from the shared memory. That's it, that's the whole personality 🫢


🌸 SYNOPSIS 🌸

void qed_mcp_read_ufp_config (struct qed_hwfn *p_hwfn , struct qed_ptt
*p_ptt );

Like, look at it. Two args. No return. Iconic behaviour honestly πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • p_hwfn β€” HW device data. The hardware's whole little identity, handed to you πŸ’œ
  • p_ptt β€” P_ptt. That's the entire description, no cap. That's all the docs give us. πŸ’€ (iykyk)

⭐ RETURN ⭐

Void. Nothing. Nada. It gives you nothing back and somehow still ate πŸ”₯ (it does its reading via the struct you passed, bestie β€” but seriously, the manpage literally just says Void so don't come for me πŸ™ˆ)


🌈 SEE ALSO 🌈

First up, the source file itself β€” literally the home base:

Kernel file ./drivers/net/ethernet/qlogic/qed/qed_mcp.h

And then the entire extended friend group 😭 like genuinely the whole group chat got invited to this function's birthday:

Like I said. The whole group chat πŸ’€πŸ’–


Ngl bestie there's no warnings, no bugs, no exit statuses on this one β€” it's a chill little reader function and we respect that 🧚

That's the page!! Sourced fresh from <bold>./drivers/net/ethernet/qlogic/qed</bold>, dated October 2026 β€” mwah, slay, periodt, go read your ufp config πŸ’…πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from