qed_print_fw...erts_results(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, you're looking at the Kernel API Manual page for qed_print_fw_asserts_results πŸ’–. She's the one who prints FW Asserts results, and yes, that is the whole mood. This page is short but every crumb matters, so let's go β€” no skimming, fr fr.

🌸 NAME 🌸

qed_print_fw_asserts_results β€” Prints FW Asserts results. πŸ’…

✨ SYNOPSIS ✨

enum dbg_status qed_print_fw_asserts_results (struct qed_hwfn *p_hwfn ,
u32 *dump_buf , u32 num_dumped_dwords , char *results_buf );

πŸŽ€ ARGUMENTS πŸŽ€

  • p_hwfn β€” HW device data. That's the hardware device data, bestie.
  • dump_buf β€” FW Asserts dump buffer, starting from the header. Starting from the header is the vibe β€” don't skip it.
  • num_dumped_dwords β€” number of dwords that were dumped. Count 'em, don't guess.
  • results_buf β€” buffer for printing the FW Asserts results. This is where the printed results hang out.

πŸ¦‹ RETURN πŸ¦‹

Error if the parsing fails, ok otherwise. So yeah: parsing fails β†’ error; parsing is fine β†’ ok. Simple, clean, no cap. ✨

🌈 SEE ALSO 🌈


mwah πŸ’‹ β€” sourced from ./drivers/net/ethernet/qlogic/qed, dated October 2026, and the footer title energy is qed_print_fw...erts_results(9) ✨🫢

πŸ“¦ where this page comes from