qed_memcpy_from(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– qed_memcpy_from β€” the kernel API manual, bestie edition πŸ’–

okay so welcome to the Kernel API Manual page for qed_memcpy_from(9) πŸŽ€ pull up a chair, grab a strawberry, and let's get into it ✨


🌸 NAME 🌸

qed_memcpy_from β€” copy n bytes from BAR using the given ptt. that's the whole gig, no cap πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void qed_memcpy_from (struct qed_hwfn *p_hwfn , struct qed_ptt *p_ptt ,
void *dest , u32 hw_addr , size_t n );

yes bestie that's the exact signature, i typed it out character for character because i love you 🫢


✨ ARGUMENTS ✨

  • p_hwfn β€” HW device data πŸ’– this is your hardware function struct, the whole vibe of the device lives here.
  • p_ptt β€” P_ptt 🌈 the ptt you're passing in, that's it, that's the arg.
  • dest β€” Destination 🎯 where the bytes are headed (in memory, not on a trip).
  • hw_addr β€” HW address πŸ’» the hardware-side address you're reading from.
  • n β€” N πŸ”’ literally the number of bytes. iconic one-letter parameter behavior, we stan.

πŸ‘‘ RETURN πŸ‘‘

Void. it returns nothing. no value, no drama, no return statement energy β€” it's giving void fr fr πŸ’€


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/net/ethernet/qlogic/qed/qed_hw.h plus the whole friend group of qed functions, all listed out because i would never leave a single one behind πŸ’œ

ngl the pretend/unpretend ones have main character energy and i'm obsessed 🧚

okay that's the whole page bestie, you ate reading this ✨ this little cutie lives in ./drivers/net/ethernet/qlogic/qed, dated October 2026, and its name is qed_memcpy_from(9) β€” mwah, slay, bye πŸ’…πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from