qed_memcpy_to(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qed_memcpy_to(9) β€” a Kernel API Manual moment πŸŽ€

okay bestie, welcome to the qed_memcpy_to(9) page, like the actual kernel API manual energy, and honestly? it's a short one but she serves. this is the "copy stuff INTO the BAR" girlie, and yes she has a p_ptt and yes we're gonna talk about it πŸ’–


✨ NAME ✨

qed_memcpy_to β€” copy n bytes to BAR using the given ptt 🫢

like, that's the whole assignment. copy. bytes. to the BAR. with a ptt. iconic.


🌸 SYNOPSIS 🌸

void qed_memcpy_to (struct qed_hwfn *p_hwfn , struct qed_ptt *p_ptt ,
u32 hw_addr , void *src , size_t n );

she's void, she takes five things, no cap πŸ€·β€β™€οΈβœ¨


πŸ¦‹ ARGUMENTS πŸ¦‹

look, the original docs are mad terse here, and I'm not about to invent lore, so here's exactly what you get:

  • p_hwfn β€” HW device data. πŸ’» (the hardware device's whole situation, basically her main character data)
  • p_ptt β€” P_ptt. πŸŽ€ (yes. that's the description. we love a minimal queen)
  • hw_addr β€” HW address. πŸ“ (the address, on the hardware)
  • src β€” Source. πŸ“€ (where the bytes are coming from)
  • n β€” N. πŸ”’ (the count. the number. the n.)
ngl the upstream descriptions are giving "wrote this at 3am before the merge window closed" 😭 but we're respecting the source material fr fr β€” no extra guesses added, bestie's honour πŸ’…

πŸ’€ RETURN πŸ’€

Void. πŸ•³οΈ

that's it. nothing comes back. she does the thing and dips, zero notes, no return value, main character exit 🌈


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/net/ethernet/qlogic/qed/qed_hw.h and her whole friend group:

it's a whole squad, go read them too πŸ§šβ€β™€οΈβœ¨


and that's the page!! shipped from ./drivers/net/ethernet/qlogic/qed, dated October 2026, filed under qed_memcpy_to(9) β€” mwah, go copy some bytes to a BAR responsibly, ily, bye πŸ’œπŸŽ€πŸ¦‹

πŸ“¦ where this page comes from