hisi_qm_wait_task_finish(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… hisi_qm_wait_task_finish β€” kernel API manual, section 9 πŸŽ€

okay so bestie, you found the page for hisi_qm_wait_task_finish(9), and we're gonna get you so comfy with it. it's a kernel API manual page (section 9, the grown-and-sexy-function one), and yes it does exactly what it says on the tin πŸ¦‹


✨ NAME ✨

hisi_qm_wait_task_finish β€” literally wait until the task is finished when removing the driver. that's it. that's the whole job. no cap πŸ’…


🌸 SYNOPSIS 🌸

void hisi_qm_wait_task_finish (struct hisi_qm *qm , struct hisi_qm_list
*qm_list );

it returns void, so like… don't go looking for a return value, she gives you nothing back and she's iconic for it 😌


🫢 ARGUMENTS 🫢

  • qm β€” the qm you need to wait on so the task can finish. this is your main character right here πŸ‘‘
  • qm_list β€” the list of all available devices. the whole squad, basically 🌈
lowkey important: this whole function is about the removing the driver moment, so it's a teardown-time vibe check, not a hot-path situation πŸ’€

🧚 SEE ALSO 🧚

the kernel file lives at ./drivers/crypto/hisilicon/qm.c and honestly the whole friend group is listed below β€” go say hi, they all live in the same file πŸ“šβœ¨


and that's the whole page, bestie β€” you ate that πŸ“ go forth and wait on your tasks responsibly, mwah πŸ’–

sign-off szn: this one's from ./drivers/crypto/hisilicon, dated October 2026, and it's page hisi_qm_wait_task_finish(9) β€” periodt πŸ’…πŸŽ€

πŸ“¦ where this page comes from