plist_last(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ plist_last(9) β€” like, the actual manual page, bestie

okay so first things first: this whole thing lives in the Kernel API Manual, and the star of the show is plist_last. yes that's the manual name, no I'm not being weird about it, it's literally in the header bestie πŸŽ€


🌸 NAME 🌸

plist_last β€” return the last node (and thus, lowest priority)

no cap, that's the whole pitch. it hands you the last node, which by plist logic is the one with the lowest priority. iconic behaviour honestly πŸ’…


✨ SYNOPSIS ✨

struct plist_node * plist_last (const struct plist_head *head );

look at her go. one function, one job, zero drama πŸ¦‹


πŸŽ€ ARGUMENTS πŸŽ€

  • head β€” the struct plist_head pointer. that's it. that's the whole argument list. give her the head of the plist and she'll do the rest 🫢

πŸ’– DESCRIPTION πŸ’–

so here's the thing, and I need you to really hear me on this one:

Assumes the plist is _not_ empty.

like, fr fr. that's the entire caveat. she is assuming there's at least one node in there. if you roll up with an empty plist… bestie. no. don't. this is not the function for that. do your vibe check with something else first πŸ˜­πŸ’€

when the plist does have nodes though? she ate. last node, lowest priority, done. main character energy πŸ”₯


🌈 SEE ALSO 🌈

the whole extended friend group, all of them are (9) pages, all of them iconic in their own way:

iykyk πŸ‘‘ literally the entire plist cinematic universe.


and that's the page!! πŸŽ‰ this little gem is filed under ./include/linux and dated October 2026, so go forth, check your plist isn't empty, and slay πŸ’…βœ¨πŸ’–

πŸ“¦ where this page comes from