finish_notification(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… finish_notification(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” yes that's the whole manual name, and yes this little function lives rent-free in it. buckle up, it's a short one but it's iconic πŸŽ€


✨ NAME ✨

finish_notification β€” literally just wraps up the notification process. that's it. that's the vibe. periodt πŸ’…


🌸 SYNOPSIS 🌸

void finish_notification (struct vdo_completion *completion );

no return value, no drama, just vibes and a single pointer πŸ¦‹


πŸ’– ARGUMENTS πŸ’–

  • completion β€” the flusher completion. that's the one. your main character struct of this whole function 🫢

🧚 DESCRIPTION 🧚

so here's the tea β˜• β€” finish_notification finishes the notification process. how, you ask? it does two (2) things, and honestly? slay:

  1. it checks if any flushes have completed βœ…
  2. then it starts the notification of the next flush request β€” but only if one came in while the current notification was already in progress πŸ”₯

like, it's giving "clean up, then see if anyone's waiting in the group chat" energy, yk? very considerate, very polite, no cap πŸ’œ

also important, don't skip this part: this callback is registered in flush_packer_callback. that's the plug. that's where it gets hooked up. iykyk ✨

ngl, this is a callback β€” so you're not out here calling it yourself in your main character arc. it gets invoked through the registration, bestie. respect the flow πŸ™ˆ

πŸŽ€ SEE ALSO πŸŽ€

Kernel file ./drivers/md/dm-vdo/flush.c β€” plus the whole friend group, and honestly they're all here, no one got left out of the group photo πŸ“Έ:


and that's the whole page, bestie β€” go forth and notify responsibly πŸ’…βœ¨

so this lil masterpiece lives down in ./drivers/md/dm-vdo, dated October 2026, and it goes by finish_notification(9). mwah, bye πŸ“πŸ«Ά

πŸ“¦ where this page comes from